TYPO3CMS
CVE-2020-11064
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 · uneditedIn TYPO3 CMS greater than or equal to 9.0.0 and less than 9.5.17 and greater than or equal to 10.0.0 and less than 10.4.2, it has been discovered that HTML placeholder attributes containing data of other database records are vulnerable to cross-site scripting. A valid backend user account is needed to exploit this vulnerability. This has been fixed in 9.5.17 and 10.4.2.
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 confidenceIn TYPO3 CMS versions 9.0.0 through 9.5.16 and 10.0.0 through 10.4.1, HTML placeholder attributes that display data from other database records are vulnerable to stored cross-site scripting (XSS). An authenticated backend user with malicious intent can inject arbitrary JavaScript code into these placeholders, which then executes when other users view the affected records.
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
TYPO3CMS
>= 9.0.0, < 9.5.17>= 10.0.0, < 10.4.2CVSS 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.
-
Check TYPO3 CMS installed versionLocate the version file or check the backend about section: typically found in composer.json, typo3/sysext/core/Classes/Information/Typo3Version.php, or via the backend admin tools > About moduleAffected if The installed version is >= 9.0.0 and < 9.5.17, or >= 10.0.0 and < 10.4.2
-
Verify backend access is exposedConfirm whether the TYPO3 backend (/typo3 or /admin) is accessible from the web. Check web server configuration or attempt to access the backend login URLAffected if The backend is publicly accessible or accessible to untrusted users
-
Identify use of HTML placeholder functionalityInspect database tables that store placeholder configurations, particularly in extensions or custom fields that render HTML attributes displaying data from related records. Check for tables containing placeholder or tt_content referencesAffected if The installation uses extensions or custom configurations that render HTML placeholders with data pulled from other database records
-
Inspect rendered HTML for unescaped attribute valuesAccess backend record views that display placeholder data from other records. View page source and examine placeholder attributes (such as title, alt, or data-* attributes) for unescaped characters like quotes, angle brackets, or script tagsAffected if Placeholder attributes contain unescaped HTML or JavaScript that could execute when viewed by other users
Your environment is affected if running a vulnerable TYPO3 version AND the backend is accessible to users who could inject malicious placeholder content that gets rendered when other users view the affected records.
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 data9.5.1710.4.2
Upgrade TYPO3 CMS to version 9.5.17, 10.4.2, or later. Alternatively, restrict backend user permissions to minimize the attack surface for malicious users.
Fix this in TYPO3
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11064 — 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-11064 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