OpenEMR allows inconsistent escaping of translation function output
openemr
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| openemr openemr |
| No fix yet |
Original 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.
From the CVE record · GitHub_M