CVE-2026-47345: TYPO3 HTML Sanitizer · Cross-site Scripting
Affects TYPO3 HTML SanitizerSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium : upgrade to 2.3.2 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.3.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade HTML Sanitizer and typo3/html-sanitizer to 2.3.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| TYPO3HTML Sanitizer | Affected
| Fixed in
|
GitHubtypo3/html-sanitizerpkg:github/typo3/html-sanitizerOther threats | Affected
| Fixed in
|
Packagisttypo3/html-sanitizerpkg:composer/typo3/html-sanitizerOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, consider applying additional input validation or output encoding controls where feasible to mitigate potential exploitation.
Description
Namespace attributes are not encoded correctly during HTML serialization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.