CVSS 3.1
9.6 criticalCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:NCVE-2026-102940 open-emr openemr
Critical (9.6) in open-emr openemr. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
On this page
OpenEMR is a free and open source electronic health records and medical practice management application. Prior to 8.4.0, controllers/C_Document.class.php write actions, including move_action_process(), do not verify the caller's access to the source document, current patient and category, or destination patient and category before Document::change_patient() performs the mutation. A low-privilege authenticated user can reassign an arbitrary document to a patient or category the user can access and then retrieve it through the normally protected read path. The reassignment occurs before a later list rendering check, so a final HTTP 403 response does not mean the unauthorized write was blocked. This issue is fixed in version 8.4.0.
Severity
- EPSS
- 0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 33rd percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-11-05. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-639 Authorization Bypass Through User-Controlled Key
- OWASP Top 10
- A01:2025 Broken Access Control
- Published
- Modified
- NVD analysis
- Analyzed
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-102940 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-102940?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-102940?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-102940 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-102940)
HTML:
<a href="https://cve.bz/cve/CVE-2026-102940"><img src="https://cve.bz/cve/badge/CVE-2026-102940.svg" alt="CVE-2026-102940"></a>
Affected
Versions
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| open-emr:openemr | before 8.4.0 |
Fix and patched versions
- Patch: https://github.com/openemr/openemr/commit/312b5d042f7fa49cc78ebed041155fba339a991c
- Patch: https://github.com/openemr/openemr/pull/13353
- Vendor advisory: https://github.com/openemr/openemr/security/advisories/GHSA-92rh-g949-4mvv
History
- Analyzed by the NVD
Changes since this site first stored the record. The same for every record: /api/public/changes.