HighGHSA-2wj9-434x-9hvpBIT-typo3-2020-11067CVE-2020-11067
Insecure Deserialization in Backend User Settings in TYPO3 CMS
Published 13 May 2020 · Updated 10 Sept 2026
Affected packages
typo3/cms-coreComposer
- Affected
- >=9.0.0 <9.5.17
- Fixed in
- 9.5.17
Update to the fixed version for your release line, for example:
composer require typo3/cms-core:^9.5.17typo3/cms-coreComposer
- Affected
- >=10.0.0 <10.4.2
- Fixed in
- 10.4.2
Update to the fixed version for your release line, for example:
composer require typo3/cms-core:^10.4.2typo3/cmsComposer
- Affected
- >=10.0.0 <10.4.2
- Fixed in
- 10.4.2
Update to the fixed version for your release line, for example:
composer require typo3/cms:^10.4.2typo3/cmsComposer
- Affected
- >=9.0.0 <9.5.17
- Fixed in
- 9.5.17
Update to the fixed version for your release line, for example:
composer require typo3/cms:^9.5.17Details
It has been discovered that backend user settings (in $BE_USER->uc) are vulnerable to insecure deserialization. In combination with vulnerabilities of 3rd party components this can lead to remote code execution. A valid backend user account is needed to exploit this vulnerability.
Update to TYPO3 versions 9.5.17 or 10.4.2 that fix the problem described.
References
- https://typo3.org/security/advisory/typo3-core-sa-2020-005
Is GHSA-2wj9-434x-9hvp in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected typo3/cms-core, and gives you the command that fixes it.
References
- Linkgithub.com/TYPO3/TYPO3.CMS/security/advisories/GHSA-2wj9-434x-9hvp
- Advisorynvd.nist.gov/vuln/detail/CVE-2020-11067
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2020-11067.yaml
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/CVE-2020-11067.yaml
- Linktypo3.org/security/advisory/typo3-core-sa-2020-005
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.