CVE Intelligence
High

CVE-2020-11069 — Cross-Site Request Forgery in TYPO3 CMS

In TYPO3 CMS 9.0.0 through 9.5.16 and 10.0.0 through 10.4.1, it has been discovered that the backend user interface and install tool are vulnerable to a same-site request forgery. A backend user can be tricked into interacting with a malicious resource an attacker previously managed to upload to the web server. Scripts are then executed with the privileges of the victims' user session. In a worst-case scenario, new admin users can be created which can directly be used by an attacker. The vulnerability is basically a cross-site request forgery (CSRF) triggered by a cross-site scripting vulnerability (XSS) - but happens on the same target host - thus, it's actually a same-site request forgery. Malicious payload such as HTML containing JavaScript might be provided by either an authenticated backend user or by a non-authenticated user using a third party extension, e.g. file upload in a contact form with knowing the target location. To be successful, the attacked victim requires an active and valid backend or install tool user session at the time of the attack. This has been fixed in 9.5.17 and 10.4.2. The deployment of additional mitigation techniques is suggested as described below. - Sudo Mode Extension This TYPO3 extension intercepts modifications to security relevant database tables, e.g. those storing user accounts or storages of the file abstraction layer. Modifications need to confirmed again by the acting user providing their password again. This technique is known as sudo mode. This way, unintended actions happening in the background can be mitigated. - https://github.com/FriendsOfTYPO3/sudo-mode - https://extensions.typo3.org/extension/sudo_mode - Content Security Policy Content Security Policies tell (modern) browsers how resources served a particular site are handled. It is also possible to disallow script executions for specific locations. In a TYPO3 context, it is suggested to disallow direct script execution at least for locations /fileadmin/ and /uploads/.

Published May 13, 2020 · Updated Oct 23, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: GitHub_M

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.7% (30-day exploitation probability)+8
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.74%
ahead of 54% of scored CVEs · Oct 27, 2026
Affects
Typo3
Typo3 and 3 more
CVSS base
8.8
High · 4 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Composer Typo3/cms-core: fixed in version 9.5.17 — github.com (GitHub Security Advisories)
  • Composer Typo3/cms-core: fixed in version 10.4.2 — github.com (GitHub Security Advisories)
  • Composer Typo3/cms: fixed in version 10.4.2 — github.com (GitHub Security Advisories)
  • Composer Typo3/cms: fixed in version 9.5.17 — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Typo3 Typo3, TYPO3 TYPO3 CMS, Composer Typo3/cms…).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. Apply the fixed version or the patch documented under Remediation.
  4. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  5. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Typo3 Typo3 ≥ 9.0.0 and ≤ 9.5.16≥ 10.0.0 and ≤ 10.4.1 Vulnerable NIST National Vulnerability Database
TYPO3 TYPO3 CMS version >= 9.0.0, < 9.5.17version >= 10.0.0, < 10.4.2 Vulnerable CVE Program (cve.org) e CISA ADP
Composer Typo3/cms ≥ 10.0.0 and < 10.4.2≥ 9.0.0 and < 9.5.17 Vulnerable GitHub Security Advisories
Composer Typo3/cms-core ≥ 9.0.0 and < 9.5.17≥ 10.0.0 and < 10.4.2 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.8 CVSS 3.1 High 2.8 5.9 nvd@nist.gov via NIST National Vulnerability Database
8.0 CVSS 3.1 High 2.1 5.9 security-advisories@github.com via NIST National Vulnerability Database
8.0 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
8.0 CVSS 3.1 High — — GitHub_M via CVE Program (cve.org) e CISA ADP
6.8 CVSS 2.0 Medium 8.6 6.4 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 8.8 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-346

Other CVEs with this weakness →

EPSS over time FIRST

Oct 23, 2026 → Oct 27, 2026 · 5 reading(s) · max 0.74%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 23, 2026 · GitHub Security Advisories
  • Affected products added · composer/typo3/cms-core, composer/typo3/cms
    Oct 23, 2026 · GitHub Security Advisories
  • Affected products added · typo3/typo3 cms
    Oct 23, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 23, 2026
  • Affected products added · typo3/typo3
    Oct 23, 2026 · NIST National Vulnerability Database
  • CVSS changed · 8.8
    Oct 23, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 23, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 23, 2026 · Alertas do Telegram
  • 2020
  • CVE published
    May 13, 2020 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 23, 2026 – Oct 23, 2026
  • 1× Official description updated · Oct 23, 2026 – Oct 23, 2026

References

6 on the record

Elsewhere on this site

Typo3
every CVE for this vendor
CWE-346
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-109162 TYPO3 CMS - Security Misconfiguration in Form Framework 15d
  • CVE-2026-85400 TYPO3 CMS - Missing Authorization in lowlevel commands Sep 8, 2026
  • CVE-2026-77132 TYPO3 CMS - Information Disclosure via Backend Localization Wizard Sep 8, 2026
  • CVE-2026-19418 TYPO3 CMS - Broken Access Control in Backend and Install Tool Aug 11, 2026
  • CVE-2026-15305 TYPO3 CMS - Unrestricted File Upload in Form Framework Jul 14, 2026
  • CVE-2026-47352 TYPO3 CMS - Broken Access Control in Backend API Jun 9, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2020-11069 is "Cross-Site Request Forgery in TYPO3 CMS", rated High. It affects Typo3 (Typo3); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.8 describes technical severity. EPSS 0.74% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.