Weak Authentication in Session Handling in typo3/cms-core
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 8.7.55, 9.5.44, 10.4.41, 11.5.33, 12.4.8
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
TYPO3 is an open source PHP based web content management system released under the GNU GPL. In typo3 installations there are always at least two different sites. Eg. first.example.org and second.example.com. In affected versions a session cookie generated for the first site can be reused on the second site without requiring additional authentication. This vulnerability has been addressed in versions 8.7.55, 9.5.44, 10.4.41, 11.5.33, and 12.4.8. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- TYPO3 typo3
From 8.0.0 · fixed in 8.7.55; From 9.0.0 · fixed in 9.5.44; From 10.0.0 · fixed in 10.4.41; From 11.0.0 · fixed in 11.5.33; From 12.0.0 · fixed in 12.4.8
- typo3/cms-corePackagist
From 8.0.0 · fixed in 8.7.55
- typo3/cms-corePackagist
From 9.0.0 · fixed in 9.5.44
- typo3/cms-corePackagist
From 10.0.0 · fixed in 10.4.41
- typo3/cms-corePackagist
From 11.0.0 · fixed in 11.5.33
- typo3/cms-corePackagist
From 12.0.0 · fixed in 12.4.8