Deserialization of Untrusted Data in TYPO3 CMS
TYPO3 CMS
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| typo3/cms-core Packagist |
|
|
| typo3/cms Packagist |
|
TYPO3 CMS
| Product | Affected | Fixed in |
|---|---|---|
| typo3/cms-core Packagist |
|
|
| typo3/cms Packagist |
|
|
In TYPO3 CMS 9.0.0 through 9.5.16 and 10.0.0 through 10.4.1, it has been discovered that backend user settings (in $BE_USER->uc) are vulnerable to insecure deserialization. In combination with vulnerabilities of third party components, this can lead to remote code execution. A valid backend user account is needed to exploit this vulnerability. This has been fixed in 9.5.17 and 10.4.2.
From the CVE record · GitHub_M
Backend user settings in TYPO3 CMS are vulnerable to insecure deserialization. An attacker with a valid backend user account can achieve remote code execution when this flaw is combined with vulnerabilities in third-party components.
Teams running TYPO3 CMS or the Packagist packages typo3/cms-core and typo3/cms in versions 9.0.0–9.5.16 or 10.0.0–10.4.1 should check their installations.