Subscriptions
Tracking
Sign in to view the affected projects.
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Thu, 26 Feb 2026 15:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Open-emr
Open-emr openemr |
|
| CPEs | cpe:2.3:a:open-emr:openemr:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Open-emr
Open-emr openemr |
|
| Metrics |
cvssV3_1
|
Wed, 25 Feb 2026 22:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 25 Feb 2026 12:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Openemr
Openemr openemr |
|
| Vendors & Products |
Openemr
Openemr openemr |
Wed, 25 Feb 2026 02:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | OpenEMR allows inconsistent escaping of translation function output | |
| Weaknesses | CWE-116 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-02-25T21:15:31.995Z
Reserved: 2025-12-29T03:00:29.276Z
Link: CVE-2026-21443
Updated: 2026-02-25T21:15:14.616Z
Status : Analyzed
Published: 2026-02-25T02:16:21.863
Modified: 2026-02-26T15:34:11.743
Link: CVE-2026-21443
No data.
OpenCVE Enrichment
Updated: 2026-02-25T11:35:15Z