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-pqg8-crx9-g8m4high8.0

Backend Same-Site Request Forgery in TYPO3 CMS

Check your stack

The advisory, in context

Meta

  • CVSS v3.1: AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C
  • CWE-352
  • CWE-346

Problem

It has been discovered that backend user interface and install tool are vulnerable to same-origin 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-origin 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 3rd party extension - e.g. file upload in a contact form with knowing the target location.

The attacked victim requires an active and valid backend or install tool user sessions at the time of the attack to be successful.

Solution

Update to TYPO3 versions 9.5.17 or 10.4.2 that mitigates the problem described.

Additional Considerations

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 by again by the acting user with providing their password again - this technique is known as "sudo mode". This way unintended actions happening in the background can be mitigated.

Content Security Policy

Content Security Policies tell (modern) browsers how resources served a particular site are handled - it also it 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/.

# in fileadmin/.htaccess
<IfModule mod_headers.c>
	Header add Content-Security-Policy "default-src 'self'; script-src 'none';"
</IfModule>

Credits

Thanks to Matteo Bonaker who reported this issue and to TYPO3 security team member 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 9.0.0 before 9.5.17

Fixed in 9.5.17

26 explicitly affected versions

v9.0.0, v9.1.0, v9.2.0, v9.2.1, v9.3.0, v9.3.1, v9.3.2, v9.3.3, v9.4.0, v9.5.0, v9.5.1, v9.5.10, v9.5.11, v9.5.12, v9.5.13, v9.5.14, v9.5.15, v9.5.16, v9.5.2, v9.5.3, v9.5.4, v9.5.5, v9.5.6, v9.5.7, v9.5.8, v9.5.9

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "9.0.0"
        },
        {
          "fixed": "9.5.17"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "v9.0.0",
    "v9.1.0",
    "v9.2.0",
    "v9.2.1",
    "v9.3.0",
    "v9.3.1",
    "v9.3.2",
    "v9.3.3",
    "v9.4.0",
    "v9.5.0",
    "v9.5.1",
    "v9.5.10",
    "v9.5.11",
    "v9.5.12",
    "v9.5.13",
    "v9.5.14",
    "v9.5.15",
    "v9.5.16",
    "v9.5.2",
    "v9.5.3",
    "v9.5.4",
    "v9.5.5",
    "v9.5.6",
    "v9.5.7",
    "v9.5.8",
    "v9.5.9"
  ]
}
Ecosystem versions

From 10.0.0 before 10.4.2

Fixed in 10.4.2

8 explicitly affected versions

v10.0.0, v10.1.0, v10.2.0, v10.2.1, v10.2.2, v10.3.0, v10.4.0, v10.4.1

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "10.0.0"
        },
        {
          "fixed": "10.4.2"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "v10.0.0",
    "v10.1.0",
    "v10.2.0",
    "v10.2.1",
    "v10.2.2",
    "v10.3.0",
    "v10.4.0",
    "v10.4.1"
  ]
}
typo3/cms Packagist
Ecosystem versions

From 10.0.0 before 10.4.2

Fixed in 10.4.2

8 explicitly affected versions

v10.0.0, v10.1.0, v10.2.0, v10.2.1, v10.2.2, v10.3.0, v10.4.0, v10.4.1

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "10.0.0"
        },
        {
          "fixed": "10.4.2"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "v10.0.0",
    "v10.1.0",
    "v10.2.0",
    "v10.2.1",
    "v10.2.2",
    "v10.3.0",
    "v10.4.0",
    "v10.4.1"
  ]
}
typo3/cms Packagist
Ecosystem versions

From 9.0.0 before 9.5.17

Fixed in 9.5.17

26 explicitly affected versions

v9.0.0, v9.1.0, v9.2.0, v9.2.1, v9.3.0, v9.3.1, v9.3.2, v9.3.3, v9.4.0, v9.5.0, v9.5.1, v9.5.10, v9.5.11, v9.5.12, v9.5.13, v9.5.14, v9.5.15, v9.5.16, v9.5.2, v9.5.3, v9.5.4, v9.5.5, v9.5.6, v9.5.7, v9.5.8, v9.5.9

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "9.0.0"
        },
        {
          "fixed": "9.5.17"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "v9.0.0",
    "v9.1.0",
    "v9.2.0",
    "v9.2.1",
    "v9.3.0",
    "v9.3.1",
    "v9.3.2",
    "v9.3.3",
    "v9.4.0",
    "v9.5.0",
    "v9.5.1",
    "v9.5.10",
    "v9.5.11",
    "v9.5.12",
    "v9.5.13",
    "v9.5.14",
    "v9.5.15",
    "v9.5.16",
    "v9.5.2",
    "v9.5.3",
    "v9.5.4",
    "v9.5.5",
    "v9.5.6",
    "v9.5.7",
    "v9.5.8",
    "v9.5.9"
  ]
}

References