How severe is GHSA-cvm2-5f78-g9m8?

No CVSS score has been assigned to GHSA-cvm2-5f78-g9m8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-cvm2-5f78-g9m8?

GHSA-cvm2-5f78-g9m8 affects the following packages: typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms-core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-cvm2-5f78-g9m8?

Update typo3/cms-core to 12.4.37 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cvm2-5f78-g9m8 is resolved across your whole dependency graph.

How do I detect GHSA-cvm2-5f78-g9m8 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-cvm2-5f78-g9m8 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-cvm2-5f78-g9m8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-cvm2-5f78-g9m8 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-cvm2-5f78-g9m8?

GHSA-cvm2-5f78-g9m8 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 15th 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-cvm2-5f78-g9m8?

GHSA-cvm2-5f78-g9m8 is classified as CWE-209 (CWE-209). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-cvm2-5f78-g9m8 published, and has it been updated?

GHSA-cvm2-5f78-g9m8 was published on September 9, 2025 and was last updated on September 9, 2025. 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

TYPO3 CMS exposes sensitive information in an error messageGHSA-cvm2-5f78-g9m8

Fix: TYPO3-CMS/core@e1e4380

GHSA-cvm2-5f78-g9m8 is a CWE-209 vulnerability in typo3/cms-core. A fix is available for typo3/cms-core — see the affected versions and patch details below.

Also known asCVE-2025-59016

Published

Sep 9, 2025

Updated

Sep 9, 2025

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Nov 6, 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-cvm2-5f78-g9m8.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs15th percentile — riskier than 15% of all scored CVEsHighest risk

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

Real-World Exposure

5 pkgs affected

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

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

Error messages containing sensitive information in the File Abstraction Layer in TYPO3 CMS versions 9.0.0-9.5.54, 10.0.0-10.4.53, 11.0.0-11.5.47, 12.0.0-12.4.36, and 13.0.0-13.4.17 allow backend users to disclose full file paths via failed low-level file-system operations.

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms-core`	≥ 9.0.0&&< 12.4.37	12.4.37`composer require typo3/cms-core:^12.4.37`
🐘Packagist	`typo3/cms-core`	≥ 10.0.0&&< 12.4.37	12.4.37`composer require typo3/cms-core:^12.4.37`
🐘Packagist	`typo3/cms-core`	≥ 11.0.0&&< 12.4.37	12.4.37`composer require typo3/cms-core:^12.4.37`
🐘Packagist	`typo3/cms-core`	≥ 12.0.0&&< 12.4.37	12.4.37`composer require typo3/cms-core:^12.4.37`
🐘Packagist	`typo3/cms-core`	≥ 13.0.0&&< 13.4.18	13.4.18`composer require typo3/cms-core:^13.4.18`

Affected Products

1 product · 5 configurations

Application

typo3typo3

≥ 13.0.0 && ≤ 13.4.18

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 12.4.37 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cvm2-5f78-g9m8 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

O3 Security · Impact-Aware SCA

Is GHSA-cvm2-5f78-g9m8 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works