CVE-2020-11067 json
Deserialization of Untrusted Data in TYPO3 CMS
published 6y ago modified last mo. also BIT-typo3-2020-11067 , EUVD-2020-0403 , GHSA-2wj9-434x-9hvp
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- packagist typo3/cms-core 9.5.17, 10.4.2
- packagist typo3/cms 9.5.17, 10.4.2
- bitnami typo3 9.5.16, 10.4.1
Is CVE-2020-11067 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.99% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.0 | AV:N/AC:M/Au:S/C:P/I:P/A:P |
| OSV | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | typo3/cms-core | >=9.0.0, <9.5.17 >=10.0.0, <10.4.2 |
9.5.17 10.4.2 |
| packagist | typo3/cms | >=10.0.0, <10.4.2 >=9.0.0, <9.5.17 |
10.4.2 9.5.17 |
| bitnami | typo3 | >=9.0.0, <9.5.16 >=10.0.0, <10.4.1 |
9.5.16 10.4.1 |
Affected products
- TYPO3 TYPO3 CMS
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
github.com
/TYPO3/TYPO3.CMS/security/advisories/GHSA-2wj9-434x-9hvp
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-11067
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2020-11067.yaml
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/typo3/cms/CVE-2020-11067.yaml
web
-
typo3.org
/security/advisory/typo3-core-sa-2020-005
web
Sources
- CVE List CVE-2020-11067
- GitHub Advisory GHSA-2wj9-434x-9hvp
- NVD CVE-2020-11067
- OSV BIT-typo3-2020-11067
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.