CVE-2026-40509: openemr · Cross-Site Request Forgery (CSRF)
Affects openemrSource GCVE Database
Not known to be exploited · CVSS 5.3 Medium.
Data as of 27 Oct 2026, 14:12 UTC
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| openemr openemr | Affected
| Fixed in– |
Description
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.
References
- github.com/openemr/openemr/security/advisories/GHSA-wffp-pj5h-xqwp (opens in a new tab)
- github.com/openemr/openemr/releases/tag/v8_3_0 (opens in a new tab)
- github.com/openemr/openemr/commit/f760adc7bddaf9d118e1a0d40590e686783ed21b (opens in a new tab)
- vulncheck.com/advisories/openemr-csrf-via-dicom-viewer-web-path-parameter (opens in a new tab)