TYPO3CMS
CVE-2021-32767
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 · uneditedTYPO3 is an open source PHP based web content management system. In versions 9.0.0 through 9.5.27, 10.0.0 through 10.4.17, and 11.0.0 through 11.3.0, user credentials may been logged as plain-text. This occurs when explicitly using log level debug, which is not the default configuration. TYPO3 versions 9.5.28, 10.4.18, 11.3.1 contain a patch for this vulnerability.
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 versions 9.x, 10.x, and 11.x log user credentials in plain-text when debug log level is explicitly enabled (non-default configuration), allowing credential exposure through debug logs.
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
>= 7.0.0, <= 7.6.51>= 8.0.0, <= 8.7.40>= 9.0.0, <= 9.5.27>= 10.0.0, <= 10.4.17>= 11.0.0, <= 11.3.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installed TYPO3 versionLocate the VERSION file in the TYPO3 root directory, or check the 'version' value in typo3conf/LocalConfiguration.php under 'SYS', or access the TYPO3 Install Tool and view System InformationAffected if The installed version falls within these ranges: 7.0.0-7.6.51, 8.0.0-8.7.40, 9.0.0-9.5.27, 10.0.0-10.4.17, or 11.0.0-11.3.0
-
Verify debug logging is enabledInspect the logging configuration in typoconf/LocalConfiguration.php (or AdditionalConfiguration.php) and look for the 'logLevel' setting under the logging configuration sectionAffected if The logLevel is set to 'debug' (or a numeric value of 0) rather than the default production level
-
Check for credential logging configurationExamine the TYPO3 logging configuration for any logger settings that record authentication events, particularly in typo3conf/LocalConfiguration.php under the 'LOG' sectionAffected if Logger rules exist that write authentication data (such as login attempts or session tokens) and debug logging is simultaneously active
A system is affected if it runs a vulnerable TYPO3 version (within the ranges listed) AND has debug logging explicitly enabled in the configuration.
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 versions 9.5.28, 10.4.18, or 11.3.1 which contain the patch, or ensure debug logging is disabled in production environments.
Fix this in TYPO3
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-32767 — 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-2021-32767 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