OpenEMR is a free and open source electronic health records and medical practice management application. Prior to version 8.0.0.3, missing authorization in the AJAX deletion endpoint interface/forms/procedure_order/handle_deletions.php allows any authenticated user, regardless of role, to irreversibly delete procedure orders, answers, and specimens belonging to any patient in the system. Version 8.0.0.3 patches the issue.
CVE-2026-34053
This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 66% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(medium)
- EG Risk
- 41(Track)EG Risk 41/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity81% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 34%
- KEV
- Not listed
Published
March 26, 2026
Last Modified
June 17, 2026
Advisory Details (3)
Auto-updated Aug 2, 2026Missing Authorization in Procedure Order AJAX Deletion Handler · Advisory · openemr/openemr · GitHub
https://github.com/openemr/openemr/security/advisories/GHSA-3vvq-pfq6-pw98v8_0_0_3
Patch available: openemr/openemr v8_0_0_3
https://github.com/openemr/openemr/releases/tag/v8_0_0_3commit 7a16b731af7d (openemr/openemr)
Patch available: openemr/openemr v8_0_0_3 (contains commit 7a16b731af7d)
https://github.com/openemr/openemr/commit/7a16b731af7d34ffd92155fe2a5692fa1a67858eWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-02 15:26 UTCEG score recompute
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-27 14:23 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
- CVE-2013-3960EG 9.9CRITICAL
- CVE-2015-10143EG 9.8CRITICAL
- CVE-2016-11036EG 9.8CRITICAL
- CVE-2018-11541EG 9.8CRITICAL
- CVE-2011-4183NVD 6.5EG 9.8CRITICAL
- CVE-2018-10251EG 9.8EPSS p91CRITICAL
- CVE-2018-1217EG 9.8EPSS p99CRITICAL
- CVE-2018-0015EG 9.8CRITICAL
- CVE-2017-12582EG 9.8CRITICAL
- CVE-2017-1000056EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-34053?
When was CVE-2026-34053 disclosed?
Is CVE-2026-34053 actively exploited?
What is the CVSS score of CVE-2026-34053?
How do I remediate CVE-2026-34053?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-34053
Is Your Infrastructure Affected by CVE-2026-34053?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.