CVE-2026-21443OpenEMR allows inconsistent escaping of translation function output
Updated under an hour ago ()
Does this affect you?
It affects openemr and 1 other product. Add what you run to find out whether that includes you.
EPSS puts the chance of exploitation in the next 30 days at 0.15%, higher than 4% of scored CVEs.
Do this next
Free account, 1 product
OpenEMR is a free and open source electronic health records and medical practice management application. Prior to version 8.0.0, the `xl()` translation function returns unescaped strings. While wrapper functions exist for escaping in different contexts (`xlt()` for HTML, `xla()` for attributes, `xlj()` for JavaScript), there are places in the codebase where `xl()` output is used directly without escaping. If an attacker could insert malicious content into the translation database, these unescaped outputs could lead to XSS. Version 8.0.0 fixes the issue.
- CVSS
- 1.2 LOW (v4.0, CNA)CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:U
- Weakness (CWE)
- CWE-116
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- 0.15% (percentile 4)
- Assigned by
- GitHub_M
- NVD analysis
- Analyzed
- Record last updated
- Feb 25, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
openemr openemr openemr:openemr (from the name) | before 8.0.0 | CNA record |
open-emr openemr open-emr:openemr | before 8.0.0 | NVD |
References
- https://github.com/openemr/openemr/security/advisories/GHSA-3f9j-cqjj-7h46x-refsource-confirm, mitigation, vendor-advisory
- https://github.com/openemr/openemr/commit/b1e3fe8a9ed8bcaf17e0b73d7fad5434f9fe36dax-refsource-misc, patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.