Cross-Site Scripting Protection bypass in HTML Sanitizer
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.5.0, 2.1.1, 10.4.33, 11.5.20, 12.1.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- TYPO3 html-sanitizer
From 1.0.0 · fixed in 1.5.0; From 2.0.0 · fixed in 2.1.1
- typo3/html-sanitizerPackagist
From 1.0.0 · fixed in 1.5.0
- typo3/html-sanitizerPackagist
From 2.0.0 · fixed in 2.1.1
- typo3/cmsPackagist
From 10.0.0 · fixed in 10.4.33
- typo3/cmsPackagist
From 11.0.0 · fixed in 11.5.20
- typo3/cmsPackagist
From 12.0.0 · fixed in 12.1.1