OpenEMR up to 7.x REST API _rest_routes_standard.inc.php request_authorization_check
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in OpenEMR up to 7.x and classified as critical. This affects the function RestConfig::request_authorization_check of the file apis/routes/_rest_routes_standard.inc.php of the component REST API. This manipulation causes authorization.
This vulnerability appears as CVE-2026-25164. The attack may be initiated remotely. There is no available exploit.
The affected component should be upgraded.
Details
A vulnerability classified as critical was found in OpenEMR up to 7.x. Affected by this vulnerability is the function RestConfig::request_authorization_check of the file apis/routes/_rest_routes_standard.inc.php of the component REST API. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
OpenEMR is a free and open source electronic health records and medical practice management application. Prior to version 8.0.0, the REST API route table in `apis/routes/_rest_routes_standard.inc.php` does not call `RestConfig::request_authorization_check()` for the document and insurance routes. Other patient routes in the same file (e.g. encounters, patients/med) call it with the appropriate ACL. As a result, any valid API bearer token can access or modify every patient's documents and insurance data, regardless of the token’s OpenEMR ACLs—effectively exposing all document and insurance PHI to any authenticated API client. Version 8.0.0 patches the issue.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-25164 since 01/29/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available.
By approaching the search of inurl:apis/routes/_rest_routes_standard.inc.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 8.0.0 eliminates this vulnerability. Applying the patch c5e1c44774156cd0d04f4e08ed6a81fe76d38e92 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
Website
- Product: https://github.com/openemr/openemr/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.2VulDB Meta Temp Score: 7.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.1
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Google Hack: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: OpenEMR 8.0.0
Patch: c5e1c44774156cd0d04f4e08ed6a81fe76d38e92
Timeline
01/29/2026 CVE reserved02/26/2026 Advisory disclosed
02/26/2026 VulDB entry created
02/26/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-f64c-h2gh-g3f9
Status: Confirmed
CVE: CVE-2026-25164 (🔒)
GCVE (CVE): GCVE-0-2026-25164
GCVE (VulDB): GCVE-100-347833
Entry
Created: 02/26/2026 01:09Changes: 02/26/2026 01:09 (68)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.