Is typo3/html-sanitizer vulnerable?

Composer typo3/html-sanitizer has 6 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

6advisories
0critical
0on CISA KEV
0no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2022-36020TYPO3 HTML Sanitizer Bypasses Cross-Site Scripting Protectionmedium6.1>=1.0.0 and <1.0.7 or >=2.0.0 and <2.0.161.0.7, 2.0.16
CVE-2023-47125Bypassing Cross-Site Scripting Protection in TYPO3 HTML Sanitizermedium4.7>=1.0.0 and <1.5.3 or >=2.0.0 and <2.1.41.5.3, 2.1.4
CVE-2023-38500By-passing Cross-Site Scripting Protection in HTML Sanitizermedium4.7>=1.0.0 and <1.5.1 or >=2.0.0 and <2.1.21.5.1, 2.1.2
CVE-2026-47345TYPO3 HTML Sanitizer allows Cross-site Scriptingmedium0.0<2.3.22.3.2
CVE-2022-23499TYPO3 HTML Sanitizer vulnerable to Cross-Site Scriptingmedium6.1>=1.0.0 and <1.5.0 or >=2.0.0 and <2.1.11.5.0, 2.1.1
CVE-2026-47344TYPO3 HTML Sanitizer allows Cross-site Scriptinglow0.0<2.3.22.3.2

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.