Insufficient Session Expiration in TYPO3's Admin ToolGHSA-wwjw-r3gj-39fq
MEDIUMFix: TYPO3/typo3@5923879GHSA-wwjw-r3gj-39fq is a medium-severity (CVSS 6) CWE-613 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’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-wwjw-r3gj-39fq.
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🐘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:H/UI:N/S:U/C:H/I:L/A:L/E:F/RL:O/RC:C(5.6)
Problem
Admin Tool sessions initiated via the TYPO3 backend user interface have not been revoked even if the corresponding user account was degraded to lower permissions or disabled completely. This way, sessions in the admin tool theoretically could have been prolonged without any limit.
Solution
Update to TYPO3 versions 9.5.35 ELTS, 10.4.29, 11.5.11 that fix the problem described above.
Credits
Thanks to Kien Hoang who reported this issue and to TYPO3 framework merger Ralf Zimmermann and TYPO3 security member Oliver Hader who fixed the issue.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/cms-core | ≥ 9.0.0&&< 9.5.35 | 9.5.35composer require typo3/cms-core:^9.5.35 |
| 🐘Packagist | typo3/cms-core | ≥ 10.0.0&&< 10.4.29 | 10.4.29composer require typo3/cms-core:^10.4.29 |
| 🐘Packagist | typo3/cms-core | ≥ 11.0.0&&< 11.5.11 | 11.5.11composer require typo3/cms-core:^11.5.11 |
| 🐘Packagist | typo3/cms | ≥ 10.0.0&&< 10.4.29 | 10.4.29composer require typo3/cms:^10.4.29 |
| 🐘Packagist | typo3/cms | ≥ 11.0.0&&< 11.5.11 | 11.5.11composer require typo3/cms:^11.5.11 |
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 9.5.35 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wwjw-r3gj-39fq 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
Is GHSA-wwjw-r3gj-39fq in your dependencies?
Find it across Packagist, including transitive dependencies.