How severe is GHSA-6f9m-v7mp-7jjq?

No CVSS score has been assigned to GHSA-6f9m-v7mp-7jjq yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6f9m-v7mp-7jjq?

GHSA-6f9m-v7mp-7jjq affects the following packages: typo3/cms (Packagist), typo3/cms (Packagist), typo3/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-6f9m-v7mp-7jjq?

Update typo3/cms to 7.6.30 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6f9m-v7mp-7jjq is resolved across your whole dependency graph.

How do I detect GHSA-6f9m-v7mp-7jjq 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-6f9m-v7mp-7jjq if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-6f9m-v7mp-7jjq actively exploited in the wild?

No public exploit code has been indexed for GHSA-6f9m-v7mp-7jjq 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-6f9m-v7mp-7jjq published, and has it been updated?

GHSA-6f9m-v7mp-7jjq 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.

Authentication Bypass in TYPO3 CMS

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

It has been discovered that TYPO3’s Salted Password system extension (which is a mandatory system component) is vulnerable to Authentication Bypass when using hashing methods which are related by PHP class inheritance. In standard TYPO3 core distributions stored passwords using the blowfish hashing algorithm can be overridden when using MD5 as the default hashing algorithm by just knowing a valid username. Per default the Portable PHP hashing algorithm (PHPass) is used which is not vulnerable.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms`	≥ 7.0.0&&< 7.6.30	7.6.30`composer require typo3/cms:^7.6.30`
🐘Packagist	`typo3/cms`	≥ 8.0.0&&< 8.7.17	8.7.17`composer require typo3/cms:^8.7.17`
🐘Packagist	`typo3/cms`	≥ 9.0.0&&< 9.3.2	9.3.2`composer require typo3/cms:^9.3.2`

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 7.6.30 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6f9m-v7mp-7jjq is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

It has been discovered that TYPO3’s Salted Password system extension (which is a mandatory system component) is vulnerable to Authentication Bypass when using hashing methods which are related by PHP class inheritance. In standard TYPO3 core distributions stored passwords using the blowfish hashing algorithm can be overridden when using MD5 as the default hashing algorithm by just knowing a valid username. Per default the Portable PHP hashing algorithm (PHPass) is used which is not vulnerable.

O3 Security · Impact-Aware SCA

Is GHSA-6f9m-v7mp-7jjq in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

Authentication Bypass in TYPO3 CMSGHSA-6f9m-v7mp-7jjq