cve.bz

CVE-2026-103935 open-emr openemr: Cross-site Scripting

8.1 highExploit referenceEPSS 0.4%Fix available

High (8.1) in open-emr openemr. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS
0.4% (unchanged from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 37th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-79 Improper Neutralization of Input During Web Page Generation (Cross-site Scripting)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-103935 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-103935?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-103935?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-103935 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-103935

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-103935](https://cve.bz/cve/badge/CVE-2026-103935.svg)](https://cve.bz/cve/CVE-2026-103935)

HTML:

<a href="https://cve.bz/cve/CVE-2026-103935"><img src="https://cve.bz/cve/badge/CVE-2026-103935.svg" alt="CVE-2026-103935"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
open-emr:openemrbefore 8.3.0

Fix and patched versions

Attack patterns (CAPEC)

  • CAPEC-63 Cross-Site Scripting (XSS) Likelihood: High · Severity: Very High
  • CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
  • CAPEC-209 XSS Using MIME Type Mismatch Severity: Medium
  • CAPEC-588 DOM-Based XSS Likelihood: High · Severity: Very High
  • CAPEC-591 Reflected XSS Likelihood: High · Severity: Very High
  • CAPEC-592 Stored XSS Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. Analyzed by the NVD

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON