Skip to main content
VulnerabilityPublished

CVE-2026-40509: OpenEMR before 8.3.0 contains a cross-site request forgery vulnerability in the DICOM viewer

Affects openemrSource GCVE Database

0
Compare
Authoritative record:CVE-2026-40509· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 8.3.0 when convenient.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.3.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 15 Nov 2026.

What to do

Upgrade openemr/openemr to 8.3.0.

Affected software

ProductAffectedFixed in
GitHubopenemr/openemrpkg:github/openemr/openemrOther threatsAffected
  • <8.3.0
Fixed in
  • 8.3.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, users should exercise caution when clicking on untrusted links while authenticated in OpenEMR. Implementing CSRF protections or input validation on the web_path parameter may mitigate the risk.

Description

OpenEMR versions prior to 8.3.0 contain a cross-site request forgery (CSRF) vulnerability in the DICOM viewer component. This vulnerability arises because the web_path GET parameter is embedded directly as a URL without proper validation or sanitization. An attacker can exploit this by crafting a malicious URL that causes an authenticated user with Patients - Documents permissions to perform unintended authenticated requests, such as forced logout or other state-changing actions.

References

Community reviews

Loading reviews…