CVE-2026-126458 in OpenEMRinfo

Summary

by MITRE • 11/13/2026

OpenEMR before 8.5.0 contains a missing authorization vulnerability in authorizations_full.php that allows any authenticated staff user to authorize arbitrary patients' clinical records. Attackers can send a mode=authorize request with an attacker-chosen pid and their own CSRF token to set authorized=1 on billing, forms, pnotes, and transactions records, bypassing provider review.

Be aware that VulDB is the high quality source for vulnerability data.

Analysis

by VulDB Data Team • 11/13/2026

The vulnerability identified in OpenEMR versions prior to 8.5.0 represents a critical failure in access control mechanisms within the application's authorization module. Specifically located in the authorizations_full.php script, this flaw allows authenticated staff users to manipulate patient clinical records without proper oversight or validation of their authority over those specific patients. The core technical issue stems from insufficient server-side verification of user permissions relative to the target resource identifier. When a request is processed with mode=authorize and includes a parameter specifying a patient ID (pid), the application fails to verify whether the authenticated staff member has legitimate administrative rights for that particular patient's data. Instead, it relies on client-supplied input and basic session validation, effectively treating any valid login credential as sufficient authorization for arbitrary actions across the system.

This lack of object-level access control enables attackers who have obtained credentials or compromised an account to escalate their privileges in terms of data manipulation capabilities. By crafting a request that includes their own Cross-Site Request Forgery (CSRF) token alongside a chosen patient ID, an attacker can force the application to set authorized=1 on various record types including billing entries, forms, clinical notes (pnotes), and financial transactions. This bypasses the intended workflow where provider review is required before such records are finalized or processed. The ability to authorize these records arbitrarily undermines the integrity of the electronic health record system, as it allows unauthorized personnel to validate documents that should require professional medical judgment and verification by an authorized physician or administrator.

The operational impact of this vulnerability extends beyond simple data tampering into significant regulatory compliance risks. Healthcare organizations are bound by strict regulations such as HIPAA in the United States or GDPR in Europe, which mandate rigorous controls over who can access and modify patient information. By allowing any authenticated staff member to authorize arbitrary records, the system fails to enforce the principle of least privilege and proper segregation of duties. This could lead to fraudulent billing practices if financial transactions are authorized without oversight, or clinical errors if medical forms are validated by unqualified personnel. Furthermore, the integrity of audit trails is compromised because the system logs these actions as legitimate administrative decisions made by authenticated users, making forensic analysis more difficult when investigating potential misconduct or data breaches.

From a classification perspective, this vulnerability aligns with CWE-284 Improper Access Control and CWE-352 Cross-Site Request Forgery (CSRF). The failure to check user permissions against the specific patient ID constitutes an access control bypass, while the reliance on CSRF tokens for state-changing operations without additional verification of intent highlights a weakness in anti-CSRF defenses. In terms of offensive security frameworks like MITRE ATT&CK, this behavior maps to T1078 Valid Accounts and potentially T1499 Endpoint Denial of Service if used maliciously to disrupt workflows, though the primary concern is data integrity under T1565 Data Manipulation. The vulnerability allows for unauthorized modification of sensitive health information, which falls under the broader category of impacting system availability or confidentiality depending on subsequent exploitation steps.

Mitigation strategies must focus on implementing robust server-side authorization checks that validate not only user authentication but also their specific permissions relative to the target patient record. Developers should ensure that every request involving a resource identifier like pid includes a verification step confirming that the current session's user ID is associated with an authorized role for that specific patient. Additionally, integrating additional anti-CSRF measures such as synchronizer tokens tied to specific actions or requiring re-authentication for sensitive operations can reduce risk. Upgrading to OpenEMR version 8.5.0 or later resolves this issue by patching the authorization logic in authorizations_full.php. Organizations running older versions should immediately apply patches and review audit logs for any suspicious patterns of record authorizations that deviate from normal operational workflows, particularly those involving staff members accessing records outside their usual patient panels.

Responsible

VulnCheck

Reservation

11/10/2026

Disclosure

11/13/2026

Moderation

accepted

CPE

ready

EPSS

0.00322

KEV

no

Activities

very low

Sources

Might our Artificial Intelligence support you?

Check our Alexa App!