Vulnerability advisory

CVE-2021-41113

Published Updated OSV record ↗

Also known as BIT-typo3-2021-41113GHSA-657m-v5vm-f6rw

Severity
  • CVSS 3.xCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected versions

Repository

Affected commitsFixed by commit
GIT github.com/TYPO3/typo3 ↗
df8ef0727dd37da723fffadea505544d53b25709 to before 0da4bf2966784c088931dbe7f8b23bb981bf00650da4bf2966784c088931dbe7f8b23bb981bf0065
Also listed as affected (3)
  • v11.4.0
  • v11.3.0
  • v11.2.0
GIT github.com/typo3/typo3 ↗
df8ef0727dd37da723fffadea505544d53b25709 to before 0da4bf2966784c088931dbe7f8b23bb981bf00650da4bf2966784c088931dbe7f8b23bb981bf0065
Not specifiedfa51999203c5e5d913ecae5ea843ccb2b95fa33f
Also listed as affected (3)
  • v11.4.0
  • v11.3.0
  • v11.2.0

Description

TYPO3 is an open source PHP based web content management system released under the GNU GPL. 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 and SameSite=lax or none: malicious evil.com invoking TYPO3 application at example.org. Update your instance to TYPO3 version 11.5.0 which addresses the problem described.

References

  • Codex
  • Claude Code
  • VS Code
  • GitHub Copilot
  • Cursor
  • Cline
  • Windsurf
  • Google Anti-gravity
  • OpenCode
  • Pi
  • Gemini CLI
  • Hermes Agent
  • Zed
  • Junie
  • Qwen Code
  • Kiro
  • Kilo Code
  • Factory Droid

Set up GitHits for your agents

Run this command:

<> bash
npx githits@latest init

What happens next:

  1. Opens your browser to authorize GitHits
  2. Asks whether to set up GitHits at the user or project level
  3. Detects your supported AI coding tools
  4. Lets you choose which tools to configure
  5. Configures the selected tools