Cyber Posture

CVE-2026-25164

HighPublic PoC

Published: 25 February 2026

Published
25 February 2026
Modified
27 February 2026
KEV Added
Patch
CVSS Score 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS Score 0.0013 32.3th percentile
Risk Priority 16 60% EPSS · 20% KEV · 20% CVSS

Description

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…

more

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.

Mitigating Controls (NIST 800-53 r5)AI

prevent

Enforces approved authorizations for logical access to patient documents and insurance data via API routes, directly preventing bypass of ACLs by valid bearer tokens.

prevent

Establishes and enforces configuration settings for REST API routes to invoke authorization checks like RestConfig::request_authorization_check().

detect

Monitors system components for unauthorized disclosure of PHI through document and insurance API routes lacking authorization enforcement.

Security SummaryAI

CVE-2026-25164 is a missing authorization vulnerability (CWE-862) in OpenEMR, a free and open-source electronic health records and medical practice management application. In versions prior to 8.0.0, the REST API route table defined in `apis/routes/_rest_routes_standard.inc.php` fails to invoke `RestConfig::request_authorization_check()` for document and insurance routes. While other patient-related routes, such as encounters and patients/med, properly enforce OpenEMR access control lists (ACLs), this omission allows any valid API bearer token to bypass ACL restrictions and access or modify documents and insurance data across all patients, exposing protected health information (PHI).

The vulnerability has a CVSS v3.1 base score of 8.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N), indicating high confidentiality and integrity impacts with low attack complexity. Exploitation requires low privileges—an attacker needs only a valid bearer token from any authenticated API client. Over networks, they can remotely read or alter every patient's documents and insurance details without user interaction, potentially leading to unauthorized PHI disclosure or manipulation in healthcare environments.

OpenEMR version 8.0.0 addresses the issue by adding the missing authorization check to the affected routes. Security practitioners should upgrade to this version immediately. Relevant advisories and patch details are available in the GitHub security advisory (GHSA-f64c-h2gh-g3f9) and the fixing commit (c5e1c44774156cd0d04f4e08ed6a81fe76d38e92).

Details

CWE(s)

Affected Products

open-emr
openemr
≤ 8.0.0

MITRE ATT&CK Enterprise TechniquesAI

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Why these techniques?

Missing authorization in OpenEMR REST API enables exploitation of a public-facing web application to bypass ACLs, allowing low-privileged authenticated attackers to remotely access and modify sensitive patient documents and insurance data.

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

References