# CVE-2020-11070: Cross-Site Scripting in SVG Sanitizer

> An attacker can execute arbitrary scripts in a victim's browser by submitting slightly invalid SVG markup that bypasses sanitization in the TYPO3 extension.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-59cf-m7v5-wh5w

## What is CVE-2020-11070?

CVE-2020-11070 is a medium-severity cross-site scripting vulnerability in TYPO3GmbH svg_sanitizer, published on 13 May 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The SVG Sanitizer extension for TYPO3 has a cross-site scripting vulnerability in versions before 1.0.3. Slightly invalid or incomplete SVG markup is not correctly processed and thus not sanitized at all. Albeit the markup is not valid it still is evaluated in browsers and leads to cross-site scripting. This is fixed in version 1.0.3.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2020-11070?

2 open source packages ship an affected version, including t3g/svg-sanitizer. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `t3g/svg-sanitizer` | Packagist | All versions | 1.0.3 |
| `t3g/svg-sanitizer` | Packagist | All versions | 1.0.3 |

Products: Typo3 Svg Sanitizer.

## How do I fix CVE-2020-11070?

Upgrade t3g/svg-sanitizer to 1.0.3 or later.

## Is CVE-2020-11070 being exploited?

There is no known exploitation of CVE-2020-11070 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-11070 and fix it if it is affected.

What it is: CVE-2020-11070 is a medium-severity cross-site scripting vulnerability in TYPO3GmbH svg_sanitizer, published on 13 May 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-11070 in the wild and no public exploit code.

Affected packages and fixed versions:
- t3g/svg-sanitizer (Packagist): affected all versions; fixed in 1.0.3
- t3g/svg-sanitizer (Packagist): affected all versions; fixed in 1.0.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-11070/ (Markdown: https://insights.sbomify.com/CVE-2020-11070/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-11070
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-11070
- OSV: https://osv.dev/vulnerability/CVE-2020-11070

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-11070/
Summaries are generated and may contain mistakes; the official description above is the record.