CVE-2026-46518 OpenEMR: Stored XSS in prescription CSS/HTML print view via patient demographics
Stored XSS in OpenEMR allows patient portal users to execute JavaScript in clinician sessions, enabling privilege escalation and session hijacking.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-46518?
CVE-2026-46518 is a high-severity cross-site scripting vulnerability in Open-Emr Openemr, published on 9 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
OpenEMR is a free and open source electronic health records and medical practice management application. Prior to version 8.0.0.1, a stored cross-site scripting vulnerability in the prescription CSS/HTML multi-print feature allows a patient portal user to execute arbitrary JavaScript in a clinician's browser session. Patient demographic fields (name, address) are rendered without output encoding in multiprintcss_header(), and portal patients can write attacker-controlled HTML directly into patient_data by calling the PUT api/patient/:num endpoint, which bypasses the intended audit review workflow. Because the XSS fires in the clinician's authenticated session on the main OpenEMR interface, the attacker can access CSRF tokens, session data, and perform actions as the clinician — crossing the patient-to-clinician trust boundary. This issue has been patched in version 8.0.0.1.
Which versions are affected by CVE-2026-46518?
It affects 1 product.
Products include Open-Emr Openemr.
How do I fix CVE-2026-46518?
No fix has been published for CVE-2026-46518 yet. Limit exposure of the affected software until one is available.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2026-46518 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46518 exists.
Other vulnerabilities in Open-Emr Openemr
- CVE-2026-24898 OpenEMR has an Unauthenticated MedEx Token Disclosure
- CVE-2026-24849 OpenEMR Arbitrary File Read Vulnerability
- CVE-2026-24908 OpenEMR has SQL Injection in Patient API Sort Parameter
- CVE-2022-2734 Improper Restriction of Rendered UI Layers or Frames in openemr/openemr
- CVE-2024-22611 SQL injection in n/a
Sources
Also known as GHSA-4gh4-q39r-45wf.