Openemr
CVE-2026-34055
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privilege OpenEMR user
-
ExploitSubmit crafted request with arbitrary note ID
-
ExecutionBypass authorization check in pnotes.inc.php
-
ImpactAccess or modify unauthorized patient notes
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Authenticated user account required on OpenEMR versions prior to 8.0.0.3. Attacker with any valid login can modify or delete patient notes belonging to other patients via web UI by manipulating note IDs. No victim interaction needed. |
| Impact | This vulnerability presents a significant real-world risk to healthcare organizations using affected OpenEMR versions. The CVSS 3.1 score of 8.1 accurately reflects the severity with network-based attack vector (AV:N), low attack complexity (AC:L), and requiring only low-level privileges (PR:L). An authenticated attacker can achieve both high confidentiality and integrity impact without user interaction. While there is no evidence of active exploitation (not in CISA KEV) or public proof-of-concept availability, the vulnerability affects medical records which are highly sensitive and regulated under HIPAA and similar frameworks. The low attack complexity and the fact that many OpenEMR instances are internet-facing make this a practical threat. Healthcare data breaches carry significant financial, legal, and reputational consequences, elevating this beyond a theoretical risk despite the lack of observed exploitation. The availability of a patch in version 8.0.0.3 makes this immediately actionable for defenders. |
| Exploit ScenarioDerived | An authenticated attacker with low-level privileges (such as a front desk staff member with limited patient access) logs into the OpenEMR web interface and intercepts or manipulates the note ID parameter in patient notes requests. By systematically iterating through note IDs or targeting specific high-value patient records, the attacker can read, modify, or delete confidential medical notes for any patient in the system regardless of whether they have legitimate access to those patients. This could enable data theft for blackmail, competitive intelligence, or manipulation of medical records to support fraudulent insurance claims or hide medical errors. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 26, 2026
OpenEMR contains an Insecure Direct Object Reference (IDOR) vulnerability in the patient notes functionality where authenticated users can modify or delete notes belonging to any patient without proper authorization checks. This affects OpenEMR versions prior to 8.0.0.3 and allows attackers with low-level privileges to access, modify, or delete sensitive medical records they should not have access to. The vulnerability has a CVSS score of 8.1 with high confidentiality and integrity impact, though there is no current evidence of active exploitation in the wild or public proof-of-concept code.
RemediationAI
Upgrade OpenEMR to version 8.0.0.3 or later, which contains patches for this IDOR vulnerability as documented in the release notes at https://github.com/openemr/openemr/releases/tag/v8_0_0_3. The specific fix is implemented in commit 214c9b4585a6f1c8c22750172d47f0e258fec0bf available at https://github.com/openemr/openemr/commit/214c9b4585a6f1c8c22750172d47f0e258fec0bf. Until patching is possible, implement strict role-based access controls, audit user permissions to ensure principle of least privilege, monitor patient note access patterns for anomalies, and restrict network access to the OpenEMR instance to trusted IP ranges only. Given the sensitivity of medical records, prioritize this upgrade and conduct a security audit to identify any unauthorized access that may have occurred prior to patching.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability exists in the legacy patient notes functions within library/pnotes.inc.php in OpenEMR, a PHP-based open source electronic health records (EHR) and medical practice management system. The root cause is classified as CWE-639 (Authorization Bypass Through User-Controlled Key), where database operations perform updates and deletes using WHERE id = ? clauses without validating that the authenticated user has authorization to access notes for that particular patient. Multiple web UI code paths accept user-controlled note IDs and pass them directly to these vulnerable functions, creating an Insecure Direct Object Reference. This represents a web UI variant of the same vulnerability class previously identified as CVE-2026-25745 in the REST API.
Know when Openemr gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
DescriptionGitHub Advisory
OpenEMR is a free and open source electronic health records and medical practice management application. Prior to version 8.0.0.3, the legacy patient notes functions in library/pnotes.inc.php perform updates and deletes using WHERE id = ? without verifying that the note belongs to a patient the user is authorized to access. Multiple web UI callers pass user-controlled note IDs directly to these functions. This is the same class of vulnerability as CVE-2026-25745 (REST API IDOR), but affects the web UI code paths. Version 8.0.0.3 patches the issue.
Executive ViewAI
OpenEMR installations are vulnerable to unauthorized access and modification of patient medical records due to an authentication bypass flaw affecting versions prior to 8.0.0.3. This exposes protected health information (PHI) to insider threats and creates significant compliance risk under HIPAA, potentially resulting in regulatory penalties and reputational damage.
Implement Web Application Firewall (WAF) rules to restrict patient notes API endpoints by user role; enable comprehensive audit logging and real-time alerting on notes access; restrict notes functionality to authorized roles only through application-level access controls; segment OpenEMR network to limit lateral movement; require multi-factor authentication for all administrative access; disable patient notes feature if operationally feasible until patch is available.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Affected Products (CPE)GitHub Advisory
Related Vulnerabilities in OpenEMR Authorization and XSS Vulnerabilities
View all 6An authenticated SQL injection vulnerability exists in OpenEMR ≤ 4.1.1 Patch 14 that allows a low-privileged attacker to
Unauthenticated token disclosure in OpenEMR before 8.0.0. CVSS 10.0. PoC and patch available.
Path traversal in OpenEMR 7.0.4 disposeDocument() allows file access. PoC available.
Path traversal in OpenEMR electronic health records before fix allows authenticated users to read arbitrary files on the
SQL injection in OpenEMR electronic health records before fix. Authenticated users can execute arbitrary SQL through the
OpenEMR 7.0.2 is vulnerable to SQL Injection via \openemr\library\classes\Pharmacy.class.php, \controllers\C_Pharmacy.cl
An issue in OpenEMR 7.0.2 allows a remote attacker to escalate privileges viaa crafted POST request using the noteid par
Information disclosure in OpenEMR 5.0.2 to before 8.0.0 exposes sensitive data. PoC and patch available.
Remote code execution in OpenEMR through 8.2.0 lets an authenticated administrator poison the document category tree so
interface/fax/fax_dispatch.php in OpenEMR 4.1.0 allows remote authenticated users to execute arbitrary commands via shel
interface/globals.php in OpenEMR 2.x, 3.x, and 4.x before 4.2.0 patch 2 allows remote attackers to bypass authentication
Authentication bypass vulnerability in portal/account/register.php in versions of OpenEMR before 5.0.1.4 allows a remote
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB