TYPO3 CMS vulnerable to User Enumeration via Response TimingGHSA-m392-235j-9r7r
MEDIUMFix: TYPO3/typo3@f0fc9c4GHSA-m392-235j-9r7r is a medium-severity (CVSS 5.3) CWE-203 vulnerability in typo3/cms-core. A fix is available for typo3/cms-core — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- 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-m392-235j-9r7r.
EPSS Exploitation Probability
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
typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms🐘typo3/cmsReal-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:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:F/RL:O/RC:C(4.9)
Problem
It has been discovered that observing response time during user authentication (backend and frontend) can be used to distinguish between existing and non-existing user accounts.
Extension authors of 3rd party TYPO3 extensions providing a custom authentication service should check if the extension is affected by the described problem. Affected extensions must implement new MimicServiceInterface::mimicAuthUser, which simulates corresponding times regular processing would usually take.
Solution
Update to TYPO3 version 7.6.58 ELTS, 8.7.48 ELTS, 9.5.37 ELTS, 10.4.32 or 11.5.16 that fix the problem described above.
Credits
Thanks to Vautia who reported this issue and to TYPO3 core & security team members Oliver Hader who fixed the issue.
References
- TYPO3-CORE-SA-2022-007
- Vulnerability Report on huntr.dev (embargoed +30 days)
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/cms-core | ≥ 7.0.0&&< 7.6.58 | 7.6.58composer require typo3/cms-core:^7.6.58 |
| 🐘Packagist | typo3/cms-core | ≥ 8.0.0&&< 8.7.48 | 8.7.48composer require typo3/cms-core:^8.7.48 |
| 🐘Packagist | typo3/cms-core | ≥ 9.0.0&&< 9.5.37 | 9.5.37composer require typo3/cms-core:^9.5.37 |
| 🐘Packagist | typo3/cms-core | ≥ 10.0.0&&< 10.4.32 | 10.4.32composer require typo3/cms-core:^10.4.32 |
| 🐘Packagist | typo3/cms-core | ≥ 11.0.0&&< 11.5.16 | 11.5.16composer require typo3/cms-core:^11.5.16 |
| 🐘Packagist | typo3/cms | ≥ 10.0.0&&< 10.4.32 | 10.4.32composer require typo3/cms:^10.4.32 |
Affected Products
typo3typo3Detection & mitigation playbook
Open-source dependencyDetect
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.58 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m392-235j-9r7r 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
Is GHSA-m392-235j-9r7r in your dependencies?
Find it across Packagist, including transitive dependencies.