CVE-2026-21443 OpenEMR allows inconsistent escaping of translation function output

Low 1.2 Published Updated

Attackers can inject malicious scripts via unescaped translation strings in OpenEMR, potentially leading to XSS attacks.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
None listed

What is CVE-2026-21443?

CVE-2026-21443 is a low-severity cross-site scripting vulnerability in Open-Emr Openemr, published on 25 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

Official description

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.

Weakness: CWE-116

Which versions are affected by CVE-2026-21443?

It affects 1 product.

Products include Open-Emr Openemr.

How do I fix CVE-2026-21443?

No fix has been published for CVE-2026-21443 yet. Limit exposure of the affected software until one is available.

Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.

Is CVE-2026-21443 being exploited?

There is no known exploitation of CVE-2026-21443 in the wild and no public exploit code.

All Open-Emr Openemr vulnerabilities

Sources

Also known as GHSA-3f9j-cqjj-7h46.

Is CVE-2026-21443 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free