dbcve.org
TYPO3CMS

CVE-2022-31047

MEDIUM · 6.5 CVSS v3.1 Published 2022-06-14
Fix available
A fix is available. Upgrade to 7.6.57 / 8.7.47 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click Patch available

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 · unedited
TYPO3 is an open source web content management system. Prior to versions 7.6.57 ELTS, 8.7.47 ELTS, 9.5.34 ELTS, 10.4.29, and 11.5.11, system internal credentials or keys (e.g. database credentials) can be logged as plaintext in exception handlers, when logging the complete exception stack trace. TYPO3 versions 7.6.57 ELTS, 8.7.47 ELTS, 9.5.34 ELTS, 10.4.29, 11.5.11 contain a fix for the problem.

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
How this class of weakness works · CWE-532

Sensitive values — secrets, tokens, session identifiers, personal data — are written into log files, so anyone with access to the logs, which is often a broad group, obtains them. It turns a routine diagnostic into a credential leak. The fix is redacting sensitive data before it is logged and tightly restricting who can read the logs.

General guidance for the sensitive information in logs class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
Affected:>= 7.0.0, < 7.6.57>= 8.0.0, < 8.7.47>= 9.0.0, < 9.5.35>= 10.0.0, < 10.4.29>= 11.0.0, < 11.5.11

CVSS 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

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.

dbcve · scoped
Upgrade available Upgrade to 7.6.57 / 8.7.47 / 9.5.35 or later
Fixed in 7.6.578.7.479.5.35
Vendor patch github.com →
Recommended fix High confidence

Upgrade to TYPO3 7.6.57 ELTS, 8.7.47 ELTS, 9.5.34 ELTS, 10.4.29, or 11.5.11 (whichever is the next major version in your current branch)

  1. 1. Identify the current TYPO3 version by checking the 'typo3/sysext/core/Classes/Core/SystemEnvironmentBuilder.php' or the install tool
  2. 2. Based on current version, determine the appropriate target fixed release: for v7.x upgrade to 7.6.57 ELTS, for v8.x upgrade to 8.7.47 ELTS, for v9.x upgrade to 9.5.34 ELTS, for v10.x upgrade to 10.4.29, or for v11.x upgrade to 11.5.11
  3. 3. Create a complete backup of the database and all files
  4. 4. Review TYPO3 upgrade documentation for your specific version jump
  5. 5. Update any third-party extensions to compatible versions
  6. 6. Perform the upgrade following standard TYPO3 upgrade procedures
  7. 7. Clear all caches after upgrade
  8. 8. Verify that sensitive data is no longer logged in exception traces
Caveat Review TYPO3 change logs for breaking changes between your version and the target version; some extensions may require updates

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-31047 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-31047 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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