CVE-2023-47127 is a medium-severity (CVSS 4.2) CWE-302 vulnerability in typo3/cms-core. A fix is available for typo3/cms-core — see the affected versions and patch details below.
Weak Authentication in Session Handling in typo3/cms-core
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 CVE-2023-47127.
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-coreReal-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
CVSS:
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N/E:X/RL:O/RC:C(4.0)
Problem
Given that there are at least two different sites in the same TYPO3 installation - for instance first.example.org and second.example.com - then a session cookie generated for the first site can be reused on the second site without requiring additional authentication.
This vulnerability primarily affects the frontend of the website. It's important to note that exploiting this vulnerability requires a valid user account.
Solution
Update to TYPO3 versions 8.7.55 ELTS, 9.5.44 ELTS, 10.4.41 ELTS, 11.5.33, 12.4.8 that fix the problem described above.
Credits
Thanks to Rémy Daniel who reported this issue, and to TYPO3 core & security team member Benjamin Franzke who fixed the issue.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/cms-core | ≥ 8.0.0&&< 8.7.55 | 8.7.55composer require typo3/cms-core:^8.7.55 |
| 🐘Packagist | typo3/cms-core | ≥ 9.0.0&&< 9.5.44 | 9.5.44composer require typo3/cms-core:^9.5.44 |
| 🐘Packagist | typo3/cms-core | ≥ 10.0.0&&< 10.4.41 | 10.4.41composer require typo3/cms-core:^10.4.41 |
| 🐘Packagist | typo3/cms-core | ≥ 11.0.0&&< 11.5.33 | 11.5.33composer require typo3/cms-core:^11.5.33 |
| 🐘Packagist | typo3/cms-core | ≥ 12.0.0&&< 12.4.8 | 12.4.8composer require typo3/cms-core:^12.4.8 |
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 8.7.55 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-47127 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 CVE-2023-47127 in your dependencies?
Find it across Packagist, including transitive dependencies.