How severe is GHSA-gj48-w74w-8gvm?

No CVSS score has been assigned to GHSA-gj48-w74w-8gvm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-gj48-w74w-8gvm?

GHSA-gj48-w74w-8gvm affects the following packages: typo3/cms (Packagist), typo3/cms (Packagist), typo3/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-gj48-w74w-8gvm?

Update typo3/cms to 6.2.29 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gj48-w74w-8gvm is resolved across your whole dependency graph.

How do I detect GHSA-gj48-w74w-8gvm 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-gj48-w74w-8gvm if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-gj48-w74w-8gvm actively exploited in the wild?

No public exploit code has been indexed for GHSA-gj48-w74w-8gvm 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-gj48-w74w-8gvm published, and has it been updated?

GHSA-gj48-w74w-8gvm was published on February 22, 2024 and was last updated on November 29, 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

Path Traversal in TYPO3 CoreGHSA-gj48-w74w-8gvm

GHSA-gj48-w74w-8gvm is a security vulnerability in typo3/cms. A fix is available for typo3/cms — see the affected versions and patch details below.

Published

Feb 22, 2024

Updated

Nov 29, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 29, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

3 pkgs affected

🐘typo3/cms🐘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

Due to a too loose type check in an API method, attackers could bypass the directory traversal check by providing an invalid UTF-8 encoding sequence.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms`	≥ 6.2.0&&< 6.2.29	6.2.29`composer require typo3/cms:^6.2.29`
🐘Packagist	`typo3/cms`	≥ 7.6.0&&< 7.6.13	7.6.13`composer require typo3/cms:^7.6.13`
🐘Packagist	`typo3/cms`	≥ 8.0.0&&< 8.4.1	8.4.1`composer require typo3/cms:^8.4.1`

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 6.2.29 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gj48-w74w-8gvm is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

Due to a too loose type check in an API method, attackers could bypass the directory traversal check by providing an invalid UTF-8 encoding sequence.

O3 Security · Impact-Aware SCA

Is GHSA-gj48-w74w-8gvm in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works