CVE-2022-23499
published 2022-12-13CVE-2022-23499: HTML sanitizer is written in PHP, aiming to provide XSS-safe markup based on explicitly allowed tags, attributes and values. In versions prior to 1.5.0 or…
PriorityP425medium6.1CVSS 3.1
AVNACLPRNUIRSCCLILAN
EPSS
0.44%
35.0th percentile
HTML sanitizer is written in PHP, aiming to provide XSS-safe markup based on explicitly allowed tags, attributes and values. In versions prior to 1.5.0 or 2.1.1, malicious markup used in a sequence with special HTML CDATA sections cannot be filtered and sanitized due to a parsing issue in the upstream package masterminds/html5. This allows bypassing the cross-site scripting mechanism of typo3/html-sanitizer. 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. This issue has been fixed in versions 1.5.0 and 2.1.1.
Affected
9 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| typo3 | cms | >= 10.0.0 < 10.4.33 | 10.4.33 |
| typo3 | cms | >= 11.0.0 < 11.5.20 | 11.5.20 |
| typo3 | cms | >= 12.0.0 < 12.1.1 | 12.1.1 |
| typo3 | html-sanitizer | — | — |
| typo3 | html-sanitizer | — | — |
| typo3 | html-sanitizer | >= 1.0.0 < 1.5.0 | 1.5.0 |
| typo3 | html-sanitizer | >= 2.0.0 < 2.1.1 | 2.1.1 |
| typo3 | html_sanitizer | 1.0.0 – 1.0.7 | — |
| typo3 | html_sanitizer | >= 2.0.0 < 2.1.1 | 2.1.1 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
TYPO3 HTML Sanitizer vulnerable to Cross-Site Scripting
ghsa·2022-12-13
CVE-2022-23499 [MEDIUM] CWE-79 TYPO3 HTML Sanitizer vulnerable to Cross-Site Scripting
TYPO3 HTML Sanitizer vulnerable to Cross-Site Scripting
### Problem
Due to a parsing issue in the upstream package [`masterminds/html5`](https://packagist.org/packages/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`](https://packagist.org/packages/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 vulnerab
OSV
TYPO3 HTML Sanitizer vulnerable to Cross-Site Scripting
osv·2022-12-13
CVE-2022-23499 [MEDIUM] TYPO3 HTML Sanitizer vulnerable to Cross-Site Scripting
TYPO3 HTML Sanitizer vulnerable to Cross-Site Scripting
### Problem
Due to a parsing issue in the upstream package [`masterminds/html5`](https://packagist.org/packages/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`](https://packagist.org/packages/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 vulnerab
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2022-12-13
Published