How severe is GHSA-h934-f4m4-wc8x?

No CVSS score has been assigned to GHSA-h934-f4m4-wc8x yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-h934-f4m4-wc8x?

GHSA-h934-f4m4-wc8x affects the following packages: typo3/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-h934-f4m4-wc8x?

Update typo3/cms to 9.5.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h934-f4m4-wc8x is resolved across your whole dependency graph.

How do I detect GHSA-h934-f4m4-wc8x in my Packagist dependencies?

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

How do I mitigate GHSA-h934-f4m4-wc8x 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-h934-f4m4-wc8x actively exploited in the wild?

No public exploit code has been indexed for GHSA-h934-f4m4-wc8x 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.

When was GHSA-h934-f4m4-wc8x published, and has it been updated?

GHSA-h934-f4m4-wc8x was published on June 5, 2024 and was last updated on December 2, 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

Typo3 Information Disclosure in Page TreeGHSA-h934-f4m4-wc8x

GHSA-h934-f4m4-wc8x is a security vulnerability in typo3/cms. A fix is available for typo3/cms — see the affected versions and patch details below.

Published

Jun 5, 2024

Updated

Dec 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘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

It has been discovered backend users not having read access to specific pages still could see them in the page tree which actually should be disallowed. A valid backend user account is needed in order to exploit this vulnerability.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms`	≥ 9.0.0&&< 9.5.6	9.5.6`composer require typo3/cms:^9.5.6`

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/cms to 9.5.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h934-f4m4-wc8x 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-h934-f4m4-wc8x in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works