OpenEMR before 8.3.0 contains a cross-site request forgery vulnerability in the DICOM viewer. The web_path GET parameter in the DICOM viewer page is embedded unsanitized as a URL without validation against expected path formats. An attacker can craft a URL that causes an authenticated user with Patients - Documents permissions to make authenticated requests to arbitrary OpenEMR endpoints, enabling forced logout and other state-changing actions.
CVE-2026-40509
Score 4.3 from GitHub Security Advisory published 2026-08-19. a secondary CVSS source baseline 4.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(high)
- EG Risk
- 34(Track)EG Risk 34/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 computedSeverity43% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 3%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 20, 2026
Advisory Details (4)
Auto-updated Aug 19, 2026OpenEMR < 8.3.0 CSRF via DICOM Viewer web_path Parameter | Advisories | VulnCheck
https://www.vulncheck.com/advisories/openemr-csrf-via-dicom-viewer-web-path-parametercommit f760adc7bdda (openemr/openemr)
Patch available: openemr/openemr v8_3_0 (contains commit f760adc7bdda)
https://github.com/openemr/openemr/commit/f760adc7bddaf9d118e1a0d40590e686783ed21bOpenEMR 8.3.0
Patch available: openemr/openemr v8_3_0
https://github.com/openemr/openemr/releases/tag/v8_3_0/library/dicom_frame.php web_path Cross-Site Request Forgery · Advisory · openemr/openemr · GitHub
https://github.com/openemr/openemr/security/advisories/GHSA-wffp-pj5h-xqwpVendor Advisories for CVE-2026-40509(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× 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-20 22:55 UTCEPSS rescore
- 2026-08-20 16:37 UTCEG score recompute
- 2026-08-20 16:37 UTCGHSA enrichment
- 2026-08-20 15:45 UTCEG score recompute
- 2026-08-20 15:45 UTCGHSA enrichment
- 2026-08-20 14:40 UTCEG score recompute
- 2026-08-20 14:40 UTCGHSA enrichment
- 2026-08-19 15:24 UTCEG score recompute
- 2026-08-19 15:09 UTCEG score recompute
- 2026-08-19 15:07 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-40509?
When was CVE-2026-40509 disclosed?
Is CVE-2026-40509 actively exploited?
What is the CVSS score of CVE-2026-40509?
How do I remediate CVE-2026-40509?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-40509
Is Your Infrastructure Affected by CVE-2026-40509?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.