TYPO3CMS
CVE-2020-11067
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 9.0.0 through 9.5.16 and 10.0.0 through 10.4.1, it has been discovered that backend user settings (in $BE_USER->uc) are vulnerable to insecure deserialization. In combination with vulnerabilities of third party components, this can lead to remote code execution. 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 confidenceTYPO3 CMS versions 9.0.0-9.5.16 and 10.0.0-10.4.1 contain an insecure deserialization vulnerability in backend user settings ($BE_USER->uc). When chained with third-party component vulnerabilities, this can lead to remote code execution. Exploitation requires a valid backend user account.
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.16>= 10.0.0, <= 10.4.1CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 TYPO3 version file. In the web root, check for the file 'typo3/sysext/core/Configuration/Composer.json' and look for the 'version' field, or check the file 'composer.json' in the web root for the typo3/cms-core version entry. Alternatively, run: composer show typo3/cms-core 2>/dev/null | grep versionAffected if The installed version is 9.0.0-9.5.16 or 10.0.0-10.4.1 (inclusive)
-
Confirm backend access is possibleDetermine if backend login URL is accessible (typically /typo3/) and if any backend user accounts exist. Check the 'be_users' database table for active accounts, or attempt to access the backend login page and verify it responds.Affected if At least one active backend user account exists and can authenticate, or the backend login interface is accessible and functional
-
Verify the vulnerable component is presentConfirm the core system extension handling user settings is installed. Check that the file typo3/sysext/core/Classes/UserSettings/ exists, which contains the $BE_USER->uc user configuration handling that contains the insecure deserialization vulnerability.Affected if The TYPO3 core is present (which it always is in affected versions), meaning the vulnerable $BE_USER->uc deserialization in user settings is in the codebase
You are affected if your TYPO3 CMS version is 9.0.0 through 9.5.16 or 10.0.0 through 10.4.1 AND you have active backend user accounts enabled in your system.
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 dataUpgrade to TYPO3 CMS version 9.5.17, 10.4.2, or later stable releases. As a defense-in-depth measure, strictly limit backend user accounts and monitor for suspicious user activity.
Fix this in TYPO3
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11067 — 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-11067 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