CVE-2020-11066

mediumpriority · track · 41EPSS 0.015 · 74 %ileEUUS
grimoire priorityP3 · Track
Exploitable?
—
no known exploitation
Likely / severe?
1.51% (74th) EPSS
CVSS 6.4 · medium
Is it mine?
10 products
Check your exposure
Who says so?
4 sources
cnnvd · enisa_euvd · osv · nvd

EPSS · scored 2026-10-27

In TYPO3 CMS greater than or equal to 9.0.0 and less than 9.5.17 and greater than or equal to 10.0.0 and less than 10.4.2, calling unserialize() on malicious user-submitted content can lead to modification of dynamically-determined object attributes and result in triggering deletion of an arbitrary directory in the file system, if it is writable for the web server. It can also trigger message submission via email using the identity of the web site (mail relay). Another insecure deserialization vulnerability is required to actually exploit mentioned aspects. This has been fixed in 9.5.17 and 10.4.2.

01

cvss

Technical severity, 0–10. One row per scoring source.

10.0
010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–critical · 6.4–10

v2.06.4mediumAV:N/AC:L/Au:N/C:N/I:P/A:Pprimary · NVD / NIST USexploitability 10 · impact 4.9
v3.110criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:Hprimary · NVD / NIST USexploitability 3.9 · impact 5.8
v3.18.7highCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:Hsecondary · ENISA EU
v3.18.7highCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:Hsecondary · security-advisories@github.comexploitability 2.2 · impact 5.8
v3.18.7highCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:Hsecondary · OSV
v3.19.1criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H/E:Usecondary · CVSS-BT (t0sche)
02

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-1321USprimaryCWE-1321USCWE-915USCWE-915US
03

affected products (10)

Products and version ranges known to be affected.

04

advisories (2)

Vendor and ecosystem advisories describing this.

  • GHSA-2rxh-h6h9-qrqcClass destructors causing side-effects when being unserialized in TYPO3 CMS2020-05-13ghsa · osvUS

    Calling unserialize() on malicious user-submitted content can result in the following scenarios: - trigger deletion of arbitrary directory in file system (if writable for web server) - trigger message submission via email using identity of web site (mail relay) Another insecure deserialization vulnerability is required to actually exploit mentioned aspects. 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-004

  • BIT-typo3-2020-110662024-03-06vendor · osvUS

    In TYPO3 CMS greater than or equal to 9.0.0 and less than 9.5.17 and greater than or equal to 10.0.0 and less than 10.4.2, calling unserialize() on malicious user-submitted content can lead to modification of dynamically-determined object attributes and result in triggering deletion of an arbitrary directory in the file system, if it is writable for the web server. It can also trigger message submission via email using the identity of the web site (mail relay). Another insecure deserialization vulnerability is required to actually exploit mentioned aspects. This has been fixed in 9.5.17 and 10.4.2.

05

also known as (5)

Other names and identifiers for this entity.

06

sources

Which sources assert this record, and when.

cnnvdenisa_euvdosvnvdNVDCVE.orgMITRE
published 2020-05-14modified 2026-06-17
08

references (7)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan