CVE-2026-34051
Improper Access Control in OpenEMR Import/Export Enables Data Theft
Publication date: 2026-03-26
Last updated on: 2026-03-26
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| open-emr | openemr | to 8.0.0.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-285 | The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. |
| CWE-425 | The web application does not adequately enforce appropriate authorization on all restricted URLs, scripts, or files. |
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to upgrade OpenEMR to version 8.0.0.3 or later, which contains the fix for this vulnerability.
The fix involves adding proper access control checks in the export and import functionality to ensure only authorized users can perform these actions.
If upgrading immediately is not possible, restrict access to the Import/Export URLs by network controls or web server configuration to prevent unauthorized direct requests.
Additionally, review and tighten user permissions to ensure that low-privilege users cannot access sensitive import/export functions.
Can you explain this vulnerability to me?
CVE-2026-34051 is a vulnerability in OpenEMR, an open source electronic health records application, where improper access control exists on the Import/Export functionality.
This flaw allows unauthorized users to bypass user interface restrictions by manipulating direct requests to perform import and export actions.
As a result, attackers with low-level privileges can access, extract, or manipulate sensitive patient data that they should not be able to handle.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows unauthorized users to bypass access controls and perform import and export operations on sensitive patient data, including bulk data extraction and manipulation.
Such unauthorized access and potential leakage of patient information can lead to non-compliance with regulations like GDPR and HIPAA, which mandate strict controls over access to personal and health data to protect patient privacy and data security.
By failing to enforce proper authorization checks, the system risks exposing sensitive health records, which could result in regulatory violations, legal consequences, and loss of trust.
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized bulk access and extraction of sensitive patient information.
Attackers can manipulate system data by importing or exporting patient data without proper authorization.
Such unauthorized actions can compromise the confidentiality and integrity of patient records, potentially exposing private health information.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by attempting to access the Import/Export functionality URLs directly, bypassing the UI restrictions, while logged in as a low-privilege user such as a Receptionist.
Specifically, you can try to send HTTP requests to the Import/Export endpoints (e.g., the URL for export_xml.php) to check if unauthorized import or export actions are allowed.
For example, using curl commands to simulate direct requests can help detect the vulnerability:
- curl -i -b cookies.txt -c cookies.txt -X GET "http://<openemr-server>/custom/export_xml.php"
- curl -i -b cookies.txt -c cookies.txt -X POST "http://<openemr-server>/custom/import_xml.php" -d @patient_data.xml
Here, cookies.txt contains the session cookies of a low-privilege user. If these requests succeed in exporting or importing patient data, it indicates the vulnerability is present.