OpenEMR before 8.3.0 Stored XSS via CAMOS Rx Print View
Affects OpenEMR before 8.3.0 for authenticated users with CAMOS encounter-form access, when stored CAMOS entries print via the non-print_html branch of rx_print.php. Fixed in 8.3.0.
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. Authenticated user with CAMOS encounter-form access OpenEMR versions before 8.3.0 Stored CAMOS content is printed via the non-print_html branch of rx_print.php
- 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 that allows authenticated users with CAMOS access to inject HTML by saving malicious CAMOS content through ajax_save.php. Attackers can store a script payload that executes unencoded when the entry is printed via the non-print_html branch of rx_print.php, performing actions and reading data as the victim user.
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
- Severity9.3/10CVSS 9.3
- 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.
Authenticated user with CAMOS encounter-form access OpenEMR versions before 8.3.0 Stored CAMOS content is printed via the non-print_html branch of rx_print.phpUpgrade to a fixed version: 8.3.0.
Timeline
- CVE published
- First seen by cve.now
- Posted on X 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-124463
Is CVE-2026-124463 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?
HTML stored in a CAMOS entry is printed without encoding, so attacker-supplied script runs in the OpenEMR origin. That script can perform actions as the affected user and read data available to that user in the current browser session.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-124463?
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, in setups where users have CAMOS encounter-form access and stored CAMOS content is printed through the non-print_html branch of rx_print.php. Check the installed OpenEMR version to see whether it falls before 8.3.0.Source: github.com, vulncheck.com
How do I fix CVE-2026-124463?
Upgrade to OpenEMR 8.3.0 or later, which contains the fix.Source: github.com, vulncheck.com