Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-33913 is a high-severity Improper Restriction of XML External Entity Reference (CWE-611) vulnerability in Open-Emr Openemr. Its CVSS base score is 7.7 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 44th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to CM-6 (Configuration Settings) and SA-11 (Developer Testing and Evaluation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-33913 is a vulnerability in OpenEMR, a free and open source electronic health records and medical practice management application. Versions prior to 8.0.0.3 are affected in the Carecoordination module, where an authenticated user can upload a crafted CCDA document containing an `<xi:include href="file:///etc/passwd" parse="text"/>` element. This enables arbitrary file reads from the server and is classified as CWE-611 (Improper Restriction of XML External Entity Reference), with a CVSS v3.1 base score of 7.7 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N).
An authenticated attacker with access to the Carecoordination module can exploit this remotely over the network with low attack complexity and low privileges required, without user interaction. Successful exploitation allows reading arbitrary files on the server, resulting in high confidentiality impact due to the vulnerability's changed scope.
OpenEMR version 8.0.0.3 patches the issue. Mitigation involves updating to this release, as detailed in the patch commit (https://github.com/openemr/openemr/commit/67e1702c41cf486af0069bdafce19860e2cd9a11), release notes (https://github.com/openemr/openemr/releases/tag/v8_0_0_3), and security advisory (https://github.com/openemr/openemr/security/advisories/GHSA-9757-3cfj-wc8q).
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-16022
Vulnerability Data
OpenEMR is a free and open source electronic health records and medical practice management application. Prior to version 8.0.0.3, an authenticated user with access to the Carecoordination module can upload a crafted CCDA document containing `<xi:include href="file:///etc/passwd" parse="text"/>` to read…
more
arbitrary files from the server. Version 8.0.0.3 patches the issue.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.5.1V15.3.2
Mitigating Controls (NIST 800-53 r5) AI
Secure configuration settings can disable external entity processing in XML parsers.
Developer testing can discover XXE flaws through targeted XML parsing tests.
Input validation can reject or sanitize XML containing external entity references.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Hardened XML parser configurations directly disable external entity resolution.
Secure SDLC practices include input validation and safe XML parser configuration that prevent XXE.
Vulnerability scanning can discover XXE flaws but does not prevent their introduction in code.
Patching eliminates XXE-vulnerable parser versions but is only one aspect of software maintenance.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development catches XXE via static analysis and dynamic XML fuzzing.
Secure coding standards require disabling DTDs and external entities in XML processing.
REACH: a disclosure-reach control sees only instances that carry a vendor-published flaw, so `finds` is at most `partial` (rule, 2026-10-17).