GIVE YOUR AGENT THE EVIDENCE

Set up in your agent.

One prompt to get started. Paste it into your coding agent to connect cve.new through MCP and bring vulnerability context into your workflow.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GIVE YOUR AGENT THE EVIDENCE

Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GHSA-657m-v5vm-f6rwhigh8.8

Cross-Site-Request-Forgery in Backend

Check your stack

The advisory, in context

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

Affected packages

Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.

Ecosystem versions

From 11.2.0 before 11.5.0

Fixed in 11.5.0

6 explicitly affected versions

v11.2.0, v11.3.0, v11.3.1, v11.3.2, v11.3.3, v11.4.0

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "11.2.0"
        },
        {
          "fixed": "11.5.0"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "v11.2.0",
    "v11.3.0",
    "v11.3.1",
    "v11.3.2",
    "v11.3.3",
    "v11.4.0"
  ]
}
typo3/cms Packagist
Ecosystem versions

From 11.2.0 before 11.5.0

Fixed in 11.5.0

6 explicitly affected versions

v11.2.0, v11.3.0, v11.3.1, v11.3.2, v11.3.3, v11.4.0

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "11.2.0"
        },
        {
          "fixed": "11.5.0"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "v11.2.0",
    "v11.3.0",
    "v11.3.1",
    "v11.3.2",
    "v11.3.3",
    "v11.4.0"
  ]
}

References