# CVE-2022-36020: TYPO3 HTML Sanitizer Bypasses Cross-Site Scripting Protection

Source: https://junglewise.ai/threats/cve-2022-36020-typo3-html-sanitizer-bypasses-cross-site-scripting-protection  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2022-09-16  
License: CC BY 4.0 with a link back

CVE-2022-36020 · Severity: low · CVSS 3.1 · Published 2022-09-16

TYPO3 HTML Sanitizer Bypasses Cross-Site Scripting Protection

Technologies: [typo3/cms (Packagist)](https://junglewise.ai/threats/technologies/packagist-typo3-cms), [typo3/cms-core (Packagist)](https://junglewise.ai/threats/technologies/typo3-cms-core), [typo3/html-sanitizer (Packagist)](https://junglewise.ai/threats/technologies/typo3-html-sanitizer). Vendors: [Packagist](https://junglewise.ai/threats/vendors/packagist).

## Quick answers

**Is CVE-2022-36020 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2022-36020 being exploited in the wild.

**How severe is CVE-2022-36020?** Low severity, with a CVSS score of 3.1, published 16 September 2022.

**Which products and versions are affected?** typo3/cms (Packagist) ECOSYSTEM:introduced=10.0.0,fixed=10.4.32; typo3/cms-core (Packagist) ECOSYSTEM:introduced=10.0.0,fixed=10.4.32; typo3/html-sanitizer (Packagist) ECOSYSTEM:introduced=1.0.0,fixed=1.0.7.

**Is there a fix for CVE-2022-36020?** Yes. typo3/cms (Packagist): upgrade to 10.4.32 or later; typo3/cms-core (Packagist): upgrade to 10.4.32 or later; typo3/html-sanitizer (Packagist): upgrade to 1.0.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2022-36020?** Check whether you run typo3/cms (Packagist), typo3/cms-core (Packagist) or typo3/html-sanitizer (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- typo3/cms (Packagist): upgrade to 10.4.32 or later

  ```sh
  composer require typo3/cms:^10.4.32
  ```

- typo3/cms-core (Packagist): upgrade to 10.4.32 or later

  ```sh
  composer require typo3/cms-core:^10.4.32
  ```

- typo3/html-sanitizer (Packagist): upgrade to 1.0.7 or later

  ```sh
  composer require typo3/html-sanitizer:^1.0.7
  ```


## Affected products

- typo3/cms (Packagist) ECOSYSTEM:introduced=10.0.0,fixed=10.4.32
- typo3/cms-core (Packagist) ECOSYSTEM:introduced=10.0.0,fixed=10.4.32
- typo3/html-sanitizer (Packagist) ECOSYSTEM:introduced=1.0.0,fixed=1.0.7

## Identifiers

- CVE-2022-36020
- GHSA-47m6-46mj-p235

## Related threats

- [The referrer enforcement introduced with TYPO3-CORE-SA-2020-006 became ineffective in TYPO3 v13.0, where TYPO3 CMS started](https://junglewise.ai/threats/cve-2026-19418-typo3-cms-broken-access-control-in-backend-and-install-tool)
- [TYPO3 CMS broken access control in Media Module](https://junglewise.ai/threats/cve-2026-49742-typo3-cms-broken-access-control-in-media-module)
- [TYPO3 CMS broken access control in Form Framework form_definition table](https://junglewise.ai/threats/cve-2026-49741-typo3-cms-broken-access-control-in-form-framework-form-definition)
- [TYPO3 CMS insecure deserialization in VariableFrontend and Registry](https://junglewise.ai/threats/cve-2026-49740-typo3-cms-insecure-deserialization-in-variablefrontend-and)
- [TYPO3 CMS path traversal in GeneralUtility::isAllowedAbsPath](https://junglewise.ai/threats/cve-2026-49738-typo3-cms-path-traversal-in-generalutility-isallowedabspath)