How severe is CVE-2022-36020?

CVE-2022-36020 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-36020?

CVE-2022-36020 affects the following packages: typo3/html-sanitizer (Packagist), typo3/html-sanitizer (Packagist), typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms (Packagist), typo3/cms (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2022-36020?

Update typo3/html-sanitizer to 1.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-36020 is resolved across your whole dependency graph.

How do I detect CVE-2022-36020 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/html-sanitizer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-36020 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2022-36020 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-36020 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-36020?

CVE-2022-36020 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 57th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-36020?

CVE-2022-36020 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2022-36020 published, and has it been updated?

CVE-2022-36020 was published on September 13, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

CVE-2022-36020 — html-sanitizer

MEDIUMFix: TYPO3/html-sanitizer@60bfdc7

CVE-2022-36020 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in typo3/html-sanitizer. A fix is available for typo3/html-sanitizer — see the affected versions and patch details below.

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

Also known asGHSA-47m6-46mj-p235

Published

Sep 13, 2022

Updated

Oct 28, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-36020.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs57th percentile — riskier than 57% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

6 pkgs affected

🐘typo3/html-sanitizer🐘typo3/html-sanitizer🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms🐘typo3/cms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/html-sanitizer`	≥ 1.0.0&&< 1.0.7	1.0.7`composer require typo3/html-sanitizer:^1.0.7`
🐘Packagist	`typo3/html-sanitizer`	≥ 2.0.0&&< 2.0.16	2.0.16`composer require typo3/html-sanitizer:^2.0.16`
🐘Packagist	`typo3/cms-core`	≥ 10.0.0&&< 10.4.32	10.4.32`composer require typo3/cms-core:^10.4.32`
🐘Packagist	`typo3/cms-core`	≥ 11.0.0&&< 11.5.16	11.5.16`composer require typo3/cms-core:^11.5.16`
🐘Packagist	`typo3/cms`	≥ 10.0.0&&< 10.4.32	10.4.32`composer require typo3/cms:^10.4.32`
🐘Packagist	`typo3/cms`	≥ 11.0.0&&< 11.5.16	11.5.16`composer require typo3/cms:^11.5.16`

Affected Products

1 product · 2 configurations

Application

html sanitizertypo3

≥ 2.0.0 && < 2.0.16

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/html-sanitizer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/html-sanitizer to 1.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-36020 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2022-36020 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Sep 13, 2022

Last updated

Oct 28, 2026

Identifiers

CVE-2022-36020

GHSA-47m6-46mj-p235

References

Advisorygithub.com · CVE 2022 36020.json Advisorygithub.com · GHSA 47m6 46mj p235 Advisorynvd.nist.gov · CVE 2022 36020 Fixgithub.com · 60bfdc7f9b394d0236e16ee4cea8372a7defa493 Webpackagist.org · html5 Webpackagist.org · html sanitizer Webgithub.com · CVE 2022 36020.yaml Webgithub.com · CVE 2022 36020.yaml Webgithub.com · CVE 2022 36020.yaml Webtypo3.org · typo3 core sa 2022 011 Packagegithub.com · html sanitizer

Related vulnerabilities

Also affects typo3/html-sanitizer

This CVE is medium severity; 4 of 5 other CVEs affecting typo3/html-sanitizer are rated as high or higher (top: moderate).

CVE-2026-47344CVE-2026-47345CVE-2023-47125CVE-2023-38500CVE-2022-23499

Also affects typo3/cms-core

This CVE is medium severity; 3 of 3 other CVEs affecting typo3/cms-core are rated as high or higher (top: high).

CVE-2026-19418CVE-2026-47352CVE-2026-47347

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026