HighGHSA-657m-v5vm-f6rwBIT-typo3-2021-41113CVE-2021-41113

Cross-Site-Request-Forgery in Backend

Published 5 Oct 2021 · Updated 8 Jul 2026

Affected packages

Affected
>=11.2.0 <11.5.0
Fixed in
11.5.0
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^11.5.0
typo3/cmsComposer
Affected
>=11.2.0 <11.5.0
Fixed in
11.5.0
Update to the fixed version for your release line, for example:composer require typo3/cms:^11.5.0

Details

> ### Meta > * CVSS: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C (8.2)

Problem

It has been discovered that the new TYPO3 v11 feature that allows users to create and share deep links in the backend user interface is vulnerable to cross-site-request-forgery.

The impact is the same as described in TYPO3-CORE-SA-2020-006 (CVE-2020-11069). However, it is not limited to the same site context and does not require the attacker to be authenticated. In a worst case scenario, the attacker could create a new admin user account to compromise the system.

To successfully carry out an attack, an attacker must trick his victim to access a compromised system. The victim must have an active session in the TYPO3 backend at that time.

The following Same-Site cookie settings in _$GLOBALS[TYPO3_CONF_VARS][BE][cookieSameSite]_ are required for an attack to be successful:

  • _SameSite=_*strict*: malicious evil.example.org invoking TYPO3 application at good.example.org
  • _SameSite=_*lax* or *none*: malicious evil.com invoking TYPO3 application at example.org

Solution

Update your instance to TYPO3 version 11.5.0 which addresses the problem described.

Credits

Thanks to Richie Lee who reported this issue and to TYPO3 core & security team members Benni Mack and Oliver Hader who fixed the issue.

References

Is GHSA-657m-v5vm-f6rw in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected typo3/cms-core, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.