OpenEMR before 8.3.0 Stored XSS via CCDA/CCD Preview XSLT Attributes
Affects OpenEMR before 8.3.0 when text/xml or application/xml is allowed in the Admin file whitelist with secure upload on. Fixed in 8.3.0. CVSS scores it High (8.6); no vendor rating is given.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 8.3.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Text/XML files must be allowed in the Admin file whitelist when secure upload is on. The payload works when attribute values avoid the character denylist used by cda.xsl. The document must be opened with the inline View rather than raw Download.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
OpenEMR before 8.3.0 contains a stored cross-site scripting vulnerability in the CCDA/CCD preview stylesheets, where cda.xsl copies event-handler attributes whose values evade a character denylist and ccd.xsl copies table-cell attributes unsanitized into preview HTML. Authenticated users can upload a crafted CCDA/CCD document with onmouseover, onclick, or onfocus handlers to execute script in a clinician's session when previewed.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.6/10CVSS 8.6
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Text/XML files must be allowed in the Admin file whitelist when secure upload is on. The payload works when attribute values avoid the character denylist used by cda.xsl. The document must be opened with the inline View rather than raw Download.Upgrade to a fixed version: 8.3.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- openemr openemr
fixed in 8.3.0
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124448
Is CVE-2026-124448 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A crafted CCDA/CCD document can carry script in its XSLT attribute values. When a clinician previews that document in OpenEMR, the script can run in their browser session. The attribute values must avoid a character denylist used by cda.xsl for the payload to work.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-124448?
openemr: before 8.3.0.Source: cve.now feed data
Am I affected, and how do I check?
OpenEMR versions before 8.3.0 are in scope. The setup also matters: text/xml or application/xml must be allowed in the Admin file whitelist (Lists files_white_list) while secure upload is on, and the document has to be opened with the inline View rather than raw Download. Check your version in the OpenEMR admin footer or the version file, and check the whitelist setting in the Admin panel.Source: github.com, vulncheck.com
How do I fix CVE-2026-124448?
Upgrade to OpenEMR 8.3.0 or later, which contains the fix.Source: github.com, vulncheck.com