CVSS 3.1
7.1 highCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:LCVE-2026-103938 open-emr openemr: Cross Site Reference Forgery
High (7.1) 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.3.0, interface/patient_file/pos_checkout_ippf.php performs state-changing void, voidall, and regen operations through GET requests without CSRF token validation. The form_checksum integrity check is conditional and is skipped when the parameter is omitted, allowing a cross-site request to force an authenticated billing user to void checkouts or regenerate invoice counters. The resulting changes can alter ledger state, financial reporting, and audit records. This issue is fixed in version 8.3.0.
Severity
- EPSS
- 0.4% (up from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 38th 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: partial, assessed 2026-11-09. 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-352 Cross-Site Request Forgery (Cross Site Reference Forgery)
- 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-103938 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-103938?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-103938?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-103938 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-103938)
HTML:
<a href="https://cve.bz/cve/CVE-2026-103938"><img src="https://cve.bz/cve/badge/CVE-2026-103938.svg" alt="CVE-2026-103938"></a>
Affected
Versions
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| open-emr:openemr | before 8.3.0 |
Fix and patched versions
- Patch: https://github.com/openemr/openemr/commit/f760adc7bddaf9d118e1a0d40590e686783ed21b
- Patch: https://github.com/openemr/openemr/pull/13197
- Vendor advisory: https://github.com/openemr/openemr/security/advisories/GHSA-p8j4-vmx9-rfhj
Attack patterns (CAPEC)
- CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
- CAPEC-111 JSON Hijacking (aka JavaScript Hijacking) Likelihood: High · Severity: High
- CAPEC-462 Cross-Domain Search Timing Severity: Medium
- CAPEC-467 Cross Site Identification Severity: Low
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.
History
- Analyzed by the NVD
Changes since this site first stored the record. The same for every record: /api/public/changes.