PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-40509 openemr CVE debrief

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.

Vendor
openemr
Product
Unknown
CVSS
MEDIUM 5.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-19
Original CVE updated
2026-09-09
Advisory published
2026-08-19
Advisory updated
2026-09-09

Who should care

Healthcare organizations using OpenEMR, particularly those with Patients - Documents permissions, should assess exposure and prioritize patching to prevent potential CSRF attacks. This includes reviewing compensating controls, monitoring for suspicious activity, and tracking exceptions. Affected operators, platforms, and security teams should be aware of the vulnerability and take action to protect their systems.

Why it matters

CVE-2026-40509 is a CSRF vulnerability in OpenEMR's DICOM viewer that allows an attacker to craft a URL causing an authenticated user to make authenticated requests to arbitrary OpenEMR endpoints. Healthcare organizations using OpenEMR should prioritize patching to prevent potential CSRF attacks.

  • An attacker can cause an authenticated user to make authenticated requests to arbitrary OpenEMR endpoints, enabling forced logout and other state-changing actions.
  • The vulnerability requires verification of affected versions and remediation priority.
  • The vulnerability requires monitoring for suspicious activity and exception tracking.

Technical summary

The web_path GET parameter in the DICOM viewer page of OpenEMR before 8.3.0 is embedded unsanitized as a URL without validation against expected path formats, allowing an attacker to craft a URL that causes an authenticated user with Patients - Documents permissions to make authenticated requests to arbitrary OpenEMR endpoints. This enables forced logout and other state-changing actions. The vulnerability requires verification of affected versions and remediation priority, and monitoring for suspicious activity and exception tracking.

Defensive priority

Healthcare organizations using OpenEMR should prioritize patching to prevent potential CSRF attacks.

Recommended defensive actions

  • Patch OpenEMR to version 8.3.0 or later
  • Restrict access to the DICOM viewer page
  • Monitor for suspicious activity
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the CSRF vulnerability in OpenEMR's DICOM viewer. The vulnerability exists in OpenEMR before version 8.3.0. The web_path GET parameter in the DICOM viewer page is embedded unsanitized as a URL without validation against expected path formats. This allows an attacker to craft a URL that causes an authenticated user with Patients - Documents permissions to make authenticated requests to arbitrary OpenEMR endpoints. Evidence is limited to CVE and NVD details.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-40509 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-40509

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-40509 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-40509

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.