OpenEMR: Stored XSS via `text()` Misuse in Double-Quoted HTML Attribute
Affects OpenEMR before 8.3.0 when the Transfer Summary or Functional & Cognitive Status form is used to store and view data. 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. Transfer Summary form or Functional & Cognitive Status form must be used to store and view the data An existing patient with an active encounter is required
- 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? →
- 16/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
Stored cross-site scripting in OpenEMR, an electronic health records application, lets a logged-in clinical user remotely plant script in a form field that runs when another clinician opens that form, potentially exposing session data and patient records. The flaw is in the transfer summary and functional/cognitive status forms and does not require any action beyond opening the affected form by the victim.
Read the original description
OpenEMR is a free and open source electronic health records and medical practice management application. Prior to 8.3.0, interface/forms/transfer_summary/new.php and interface/forms/functional_cognitive_status/new.php render stored transfer_to, code, and codetext values with text(), which uses ENT_NOQUOTES, inside double-quoted HTML value attributes. An authenticated clinical user can store a value containing a double quote that escapes the attribute and injects event-handler markup when another clinician opens the form. Successful exploitation can expose session data and protected health information or permit patient-record actions in the victim's session. This issue is fixed in version 8.3.0.
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.1/10CVSS 8.1
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Transfer Summary form or Functional & Cognitive Status form must be used to store and view the data An existing patient with an active encounter is requiredUpgrade 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 4
- Advisory
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-103935
Is CVE-2026-103935 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?
Two OpenEMR forms place stored field data inside double-quoted HTML value attributes using text(), so data saved to those fields can include script that is carried into the page when it is viewed.Source: github.com
Which versions are affected by CVE-2026-103935?
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 affected. The setup involves the Transfer Summary form or the Functional & Cognitive Status form storing and displaying data for an existing patient with an active encounter. Compare the installed OpenEMR version with 8.3.0 to see whether it falls in the affected range.Source: github.com
How do I fix CVE-2026-103935?
Upgrade to OpenEMR 8.3.0 or later, which contains the fix.Source: github.com