Cross-Site Scripting in SVG Sanitizer

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2020-11070: 0.54% estimated exploitation activity in the next 30 days; percentile 45.48 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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. An updated version 1.0.3 is available from the TYPo3 extension manager and at https://extensions.typo3.org/extension/download/svgsanitizer/1.0.3/zip/ Users of the extension are advised to update the extension as soon as possible.

Published by the source

13 May 2020, 22:17 UTC

Last modified by the source

9 Jan 2023, 05:02 UTC

Source last checked

26 Oct 2026, 13:56 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-59cf-m7v5-wh5w

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-11070

Advisory: Cross-Site Scripting in SVG Sanitizer
IDs: CVE-2020-11070, GHSA-59cf-m7v5-wh5w
Record: https://patchnext.com/advisories/cve-2020-11070 (revision 1, source checked 26 Oct 2026, 13:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: t3g/svg-sanitizer 1.0.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist t3g/svg-sanitizer: affected < 1.0.3; fixed in 1.0.3

## Suggested inspection (read-only)
- Packagist t3g/svg-sanitizer: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on t3g/svg-sanitizer.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-59cf-m7v5-wh5w (GitHub-reviewed advisory GHSA-59cf-m7v5-wh5w lists affected ranges: Packagist t3g/svg-sanitizer >=0 <1.0.3)

Commands are suggestions: review each one before running it.