Bypassing Cross-Site Scripting Protection in TYPO3 HTML Sanitizer
Published 14 Nov 2023 · Updated 10 Sept 2026
Affected packages
- Affected
- >=1.0.0 <1.5.3
- Fixed in
- 1.5.3
composer require typo3/html-sanitizer:^1.5.3- Affected
- >=2.0.0 <2.1.4
- Fixed in
- 2.1.4
composer require typo3/html-sanitizer:^2.1.4Details
> ### CVSS: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC:C (4.4)
Problem
DOM processing instructions are not handled correctly. This allows bypassing the cross-site scripting mechanism of `typo3/html-sanitizer`.
Solution
Update to typo3/html-sanitizer versions 1.5.3 or 2.1.4 that fix the problem described.
Credits
Thanks to Yaniv Nizry and Niels Dossche who reported this issue, and to TYPO3 core & security team member Oliver Hader who fixed the issue.
References
Is GHSA-mm79-jhqm-9j54 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected typo3/html-sanitizer, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.