typo3/html-sanitizer vulnerabilities
HTML sanitizer aiming to provide XSS-safe markup based on explicitly allowed tags, attributes and values.
- Registry
- Composer
- Latest
- 2.3.2
- License
- MIT
6 known advisories
The latest version, 2.3.2, is not affected by any of them. Projects on older versions may be.
composer require typo3/html-sanitizer:^2.3.2Security advisories for typo3/html-sanitizer
TYPO3 HTML Sanitizer allows Cross-site Scripting
- Affected
- <2.3.2
- Fixed in
- 2.3.2
TYPO3 HTML Sanitizer allows Cross-site Scripting
- Affected
- <2.3.2
- Fixed in
- 2.3.2
Bypassing Cross-Site Scripting Protection in TYPO3 HTML Sanitizer
- Affected
- >=1.0.0 <1.5.3 · >=2.0.0 <2.1.4
- Fixed in
- 1.5.3, 2.1.4
By-passing Cross-Site Scripting Protection in HTML Sanitizer
- Affected
- >=1.0.0 <1.5.1 · >=2.0.0 <2.1.2
- Fixed in
- 1.5.1, 2.1.2
TYPO3 HTML Sanitizer vulnerable to Cross-Site Scripting
- Affected
- >=1.0.0 <1.5.0 · >=2.0.0 <2.1.1
- Fixed in
- 1.5.0, 2.1.1
TYPO3 HTML Sanitizer Bypasses Cross-Site Scripting Protection
- Affected
- >=1.0.0 <1.0.7 · >=2.0.0 <2.0.16
- Fixed in
- 1.0.7, 2.0.16
Which of your client projects still run an old typo3/html-sanitizer?
NPMscan reads the composer.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Composer packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Composer registry.