CVE-2022-23499

Problem

Due to a parsing issue in the upstream package masterminds/html5, malicious markup used in a sequence with special HTML CDATA sections cannot be filtered and sanitized. This allows bypassing the cross-site scripting mechanism of typo3/html-sanitizer.

Besides that, the upstream package masterminds/html5 provides HTML raw text elements (script, style, noframes, noembed and iframe) as DOMText nodes, which were not processed and sanitized further. None of the mentioned elements were defined in the default builder configuration, that's why only custom behaviors, using one of those tag names, were vulnerable to cross-site scripting.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2022-23499 has a CVSS score of 6.1 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.5.0, 2.1.1, 10.4.33, 11.5.20, 12.1.1); upgrading removes the vulnerable code path.

Kodem intelligence

Update to typo3/html-sanitizer versions 1.5.0 or 2.1.1 that fix the problem described.

1. What is CVE-2022-23499? CVE-2022-23499 is a medium-severity cross-site scripting (XSS) vulnerability in typo3/html-sanitizer (composer), affecting versions >= 1.0.0, < 1.5.0. It is fixed in 1.5.0, 2.1.1, 10.4.33, 11.5.20, 12.1.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2022-23499? CVE-2022-23499 has a CVSS score of 6.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2022-23499?
   • typo3/html-sanitizer (composer) (versions >= 1.0.0, < 1.5.0)
   • typo3/cms (composer) (versions >= 10.0.0, < 10.4.33)
4. Is there a fix for CVE-2022-23499? Yes. CVE-2022-23499 is fixed in 1.5.0, 2.1.1, 10.4.33, 11.5.20, 12.1.1. Upgrade to this version or later.
5. Is CVE-2022-23499 exploitable, and should I be worried? Whether CVE-2022-23499 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-23499 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-23499?
   • Upgrade typo3/html-sanitizer to 1.5.0 or later
   • Upgrade typo3/html-sanitizer to 2.1.1 or later
   • Upgrade typo3/cms to 10.4.33 or later
   • Upgrade typo3/cms to 11.5.20 or later
   • Upgrade typo3/cms to 12.1.1 or later

Other vulnerabilities in typo3/html-sanitizer