Skip to content
Fencer Vulns
medium 6.1

CVE-2022-36020 json

Bypass of Cross-Site Scripting Protection in typo3/html-sanitizer

published 2022-09-13 4 y ago modified 2026-06-17 4 mo ago also GHSA-47m6-46mj-p235 , EUVD-2022-6685

cvss
6.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 58%
public exploits
0
none known

Summary

The typo3/html-sanitizer package is an HTML sanitizer, written in PHP, aiming to provide XSS-safe markup based on explicitly allowed tags, attributes and values. Due to a parsing issue in the upstream package `masterminds/html5`, malicious markup used in a sequence with special HTML comments cannot be filtered and sanitized. This allows for a bypass of the cross-site scripting mechanism of `typo3/html-sanitizer`. This issue has been addressed in versions 1.0.7 and 2.0.16 of the `typo3/html-sanitizer` package. Users are advised to upgrade. There are no known workarounds for this issue.

Patch / fix

  • packagist typo3/html-sanitizer 1.0.7, 2.0.16
  • packagist typo3/cms-core 10.4.32, 11.5.16
  • packagist typo3/cms 10.4.32, 11.5.16
  • typo3 html_sanitizer 1.0.7, 2.0.16

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
18 mo ago

Exploit prediction

0.84% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
GitHub 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
packagist typo3/html-sanitizer
>=1.0.0, <1.0.7
>=2.0.0, <2.0.16
1.0.7
2.0.16
packagist typo3/cms-core
>=10.0.0, <10.4.32
>=11.0.0, <11.5.16
10.4.32
11.5.16
packagist typo3/cms
>=10.0.0, <10.4.32
>=11.0.0, <11.5.16
10.4.32
11.5.16

Affected products

  • TYPO3 html-sanitizer

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.