Svg SanitizerApplication · TYPO3
CVE-2020-11070
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe SVG Sanitizer extension for TYPO3 versions before 1.0.3 fails to properly sanitize malformed or incomplete SVG markup. When the sanitizer encounters invalid SVG content, it skips processing entirely, allowing malicious markup to pass through unescaped. Browsers then render and execute this markup, leading to cross-site scripting.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Svg SanitizerApplication
< 1.0.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the TYPO3 SVG Sanitizer extensionIn the TYPO3 backend, navigate to the Extension Manager or check the file system for the 'svg_sanitizer' extension directory (typically in typo3conf/ext/ or vendor/ typo3/).Affected if The extension directory named 'svg_sanitizer' or similar SVG sanitization extension exists in the TYPO3 installation.
-
Determine the installed extension versionOpen the extension's composer.json or ext_emconf.php file and locate the 'version' or 'version' field, or check the Extension Manager for the installed version number.Affected if The version number is lower than 1.0.3 (for example, 1.0.2, 1.0.1, 1.0.0, or no version displayed).
-
Identify if SVG file uploads are processedReview the TYPO3 system configuration and any custom file upload handlers to confirm whether SVG files are accepted as uploads or processed by the system.Affected if SVG files are permitted as uploads or processed by any TYPO3 content element, extension, or custom configuration.
-
Inspect SVG sanitization configurationCheck the extension configuration in TYPO3 for any 'SvgSanitizer' settings, or review the source code for calls to the sanitizer service that process SVG content.Affected if SVG processing is configured and the SvgSanitizer service is invoked without additional validation after the extension's sanitizer runs.
The environment is affected if the TYPO3 SVG Sanitizer extension version is below 1.0.3 and SVG files are being processed or accepted as uploads.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.0.3
Upgrade the TYPO3 SVG Sanitizer extension to version 1.0.3 or later, which properly handles and sanitizes even malformed SVG content before rendering.
Fix this in Svg Sanitizer
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA0.5 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11070 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-11070 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data