How severe is GHSA-fh99-4pgr-8j99?

GHSA-fh99-4pgr-8j99 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-fh99-4pgr-8j99?

GHSA-fh99-4pgr-8j99 affects the following packages: typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms (Packagist), typo3/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-fh99-4pgr-8j99?

Update typo3/cms-core to 7.6.57 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fh99-4pgr-8j99 is resolved across your whole dependency graph.

How do I detect GHSA-fh99-4pgr-8j99 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-fh99-4pgr-8j99 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-fh99-4pgr-8j99 actively exploited in the wild?

No public exploit code has been indexed for GHSA-fh99-4pgr-8j99 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-fh99-4pgr-8j99?

GHSA-fh99-4pgr-8j99 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 67th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-fh99-4pgr-8j99?

GHSA-fh99-4pgr-8j99 is classified as CWE-532 (CWE-532), CWE-209 (CWE-209). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-fh99-4pgr-8j99 published, and has it been updated?

GHSA-fh99-4pgr-8j99 was published on June 17, 2022 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

Insertion of Sensitive Information into Log File in typo3/cms-coreGHSA-fh99-4pgr-8j99

MEDIUMFix: TYPO3/typo3@c93ea69

GHSA-fh99-4pgr-8j99 is a medium-severity (CVSS 5.3) CWE-532 vulnerability in typo3/cms-core. A fix is available for typo3/cms-core — see the affected versions and patch details below.

Also known asBIT-typo3-2022-31047CVE-2022-31047

Published

Jun 17, 2022

Updated

Feb 16, 2024

Affected

7 pkgs

Patched

7 / 7

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-fh99-4pgr-8j99.

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk+0.02%

Lower risk than most CVEs67th percentile — riskier than 67% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

7 pkgs affected

🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms🐘typo3/cms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Meta

CVSS: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N/E:F/RL:O/RC:C (4.9)

Problem

It has been discovered that system internal credentials or keys (e.g. database credentials) have been logged as plaintext in exception handlers, when logging the complete exception stack trace.

Solution

Update to TYPO3 versions 7.6.57 ELTS, 8.7.47 ELTS, 9.5.35 ELTS, 10.4.29, 11.5.11 that fix the problem described above.

Credits

Thanks to Marco Huber who reported this issue and to TYPO3 security member Torben Hansen who fixed the issue.

References

TYPO3-CORE-SA-2022-002

Affected Packages

7 total 7 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms-core`	≥ 7.0.0&&< 7.6.57	7.6.57`composer require typo3/cms-core:^7.6.57`
🐘Packagist	`typo3/cms-core`	≥ 8.0.0&&< 8.7.47	8.7.47`composer require typo3/cms-core:^8.7.47`
🐘Packagist	`typo3/cms-core`	≥ 9.0.0&&< 9.5.35	9.5.35`composer require typo3/cms-core:^9.5.35`
🐘Packagist	`typo3/cms-core`	≥ 10.0.0&&< 10.4.29	10.4.29`composer require typo3/cms-core:^10.4.29`
🐘Packagist	`typo3/cms-core`	≥ 11.0.0&&< 11.5.11	11.5.11`composer require typo3/cms-core:^11.5.11`
🐘Packagist	`typo3/cms`	≥ 10.0.0&&< 10.4.29	10.4.29`composer require typo3/cms:^10.4.29`

Affected Products

1 product · 5 configurations

Application

typo3typo3

≥ 11.0.0 && < 11.5.11

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/cms-core to 7.6.57 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fh99-4pgr-8j99 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

> ### Meta > * CVSS: `CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N/E:F/RL:O/RC:C` (4.9) ### Problem It has been discovered that system internal credentials or keys (e.g. database credentials) have been logged as plaintext in exception handlers, when logging the complete exception stack trace. ### Solution Update to TYPO3 versions 7.6.57 ELTS, 8.7.47 ELTS, 9.5.35 ELTS, 10.4.29, 11.5.11 that fix the problem described above. ### Credits Thanks to Marco Huber who reported this issue and to TYPO3 security member Torben Hansen who fixed the issue. ### References * [TYPO3-CORE-SA-2022-002](https:

O3 Security · Impact-Aware SCA

Is GHSA-fh99-4pgr-8j99 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

CWE Classification

CWE-532CWE-532 CWE-209CWE-209

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Jun 17, 2022

Last updated

Feb 16, 2024

Identifiers

GHSA-fh99-4pgr-8j99

BIT-typo3-2022-31047

References

Advisorynvd.nist.gov · CVE 2022 31047 Webgithub.com · GHSA fh99 4pgr 8j99 Webgithub.com · c93ea692e7dfef03b7c50fe5437487545bee4d6a Webgithub.com · CVE 2022 31047.yaml Webtypo3.org · typo3 core sa 2022 002 Packagegithub.com · core

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting typo3/cms-core are rated as high or higher (top: high).

CVE-2026-19418CVE-2026-47352CVE-2026-47347CVE-2026-47343CVE-2026-49740CVE-2026-47348CVE-2026-49742CVE-2026-47349

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 16, 2024

Insertion of Sensitive Information into Log File in typo3/cms-coreGHSA-fh99-4pgr-8j99

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Meta

Problem

Solution

Credits

References

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-fh99-4pgr-8j99 in your dependencies?