TYPO3 CMS - Insecure Deserialization in Core API
- 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 10.4.57, 11.5.51, 12.4.46, 13.4.31, 14.3.3
- 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's cache frontend (VariableFrontend) and persistent key-value store (Registry) deserialized PHP payloads without integrity validation or class restrictions. An attacker with write access to the underlying storage backend (cache store or sys_registry database table) could inject a crafted serialized payload to trigger PHP Object Injection, potentially exploiting a gadget chain to achieve Remote Code Execution or other high-impact effects. Exploiting this vulnerability requires direct local write access to the storage, such as the SQL database or file system. This issue affects TYPO3 CMS versions before 10.4.57, 11.0.0-11.5.50, 12.0.0-12.4.45, 13.0.0-13.4.30 and 14.0.0-14.3.2.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- typo3/cms-core
fixed in 10.4.57; From 11.0.0 · fixed in 11.5.51; From 12.0.0 · fixed in 12.4.46; From 13.0.0 · fixed in 13.4.31; From 14.0.0 · fixed in 14.3.3
- typo3/cms-corePackagist
fixed in 10.4.57
- typo3/cms-corePackagist
From 11.0.0 · fixed in 11.5.51
- typo3/cms-corePackagist
From 12.0.0 · fixed in 12.4.46
- typo3/cms-corePackagist
From 13.0.0 · fixed in 13.4.31
- typo3/cms-corePackagist
From 14.0.0 · fixed in 14.3.3