Advisory record · GHSA-fh99-4pgr-8j99

Insertion of Sensitive Information into Log File in typo3/cms-core

CVSS 5.3 MediumEPSS 0.011 · 67th percentile

Published by the GitHub Advisory Database at 17 Jun 2022, 20:55 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
typo3/cms-corePackagist>=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.117.6.57, 8.7.47, 9.5.35, 10.4.29, 11.5.11
typo3/cmsPackagist>=10.0.0, <10.4.29 || >=11.0.0, <11.5.1110.4.29, 11.5.11
Identifiers
GHSA-fh99-4pgr-8j99 · BIT-typo3-2022-31047 · CVE-2022-31047 · PKSA-jbmh-6415-zvcd · PKSA-sy4v-bxfk-mjjn
Weakness (CWE)
CWE-209 · CWE-532
Published
17 Jun 2022
Updated
16 Feb 2024

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

TYPO3 CMS core (typo3/cms-core, and typo3/cms for versions 10.0.0 to before 10.4.29 and 11.0.0 to before 11.5.11) logs system credentials or keys, such as database credentials, in plaintext within exception stack traces. The source does not describe the attacker's required access, but the flaw exposes sensitive data to anyone who can read the log files. Upgrade typo3/cms-core to 7.6.57, 8.7.47, 9.5.35, 10.4.29, or 11.5.11, and upgrade typo3/cms to 10.4.29 or 11.5.11.

Written 4 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.3 Medium 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.011, the 67th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:32 UTC First seen by agentprime
  2. 31 Oct 2026, 14:32 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.