Stored XSS via unescaped translation output
Published Feb 25, 2026 · Updated Feb 25, 2026
Stored XSS in OpenEMR before 8.0.0 allows attackers to execute scripts in another user’s browser via malicious translation data. The xl() function returns translation strings without context-specific escaping, and callers place them directly into HTML, XML, and JavaScript output. Exploitation requires write access to translation tables and a user to load affected output, limiting impact to script execution in that user’s browser context.
Summary
What happened
Stored XSS in OpenEMR before 8.0.0 allows attackers to execute scripts in another user’s browser via malicious translation data. The xl() function returns translation strings without context-specific escaping, and callers place them directly into HTML, XML, and JavaScript output. Exploitation requires write access to translation tables and a user to load affected output, limiting impact to script execution in that user’s browser context.
The record
- CVE
- CVE-2026-21443
- Published
- Feb 25, 2026
- Updated
- Feb 25, 2026
- Vendor
- OpenEMR Foundation
- Product
- OpenEMR
- Classifications
- CWE-116, T1203
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Feb 25, 2026CVE publishedPublication date reported by the CVE source.
- Feb 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 8.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo