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-p4xx-m758-3hpxlow3.3

TYPO3 CMS Webhooks Server Side Request Forgery

Check your stack

The advisory, in context

Problem

Webhooks are inherently vulnerable to Server-Side Request Forgery (SSRF), which can be exploited by adversaries to target internal resources (e.g., localhost or other services on the local network). While this is not a vulnerability in TYPO3 itself, it may enable attackers to blindly access systems that would otherwise be inaccessible. An administrator-level backend user account is required to exploit this vulnerability.

Solution

Update to TYPO3 versions 12.4.31 LTS, 13.4.12 LTS that fix the problem described.

[!IMPORTANT]

Manual actions required

To mitigate potential SSRF risks via webhooks, it is recommended to explicitly allow access only to trusted hosts. This can be achieved by configuring the allowlist in $GLOBALS['TYPO3_CONF_VARS']['HTTP']['allowed_hosts']['webhooks'].

If the allowlist is not defined or set to null, all requests will be allowed. If the allowlist is an empty array, all requests will be blocked.

By default, the factory setting allows all requests. This prevents existing webhooks from failing after upgrading to the affected TYPO3 versions. Administrators must configure this setting manually to enforce restrictions.

Credits

Thanks to the National Cyber Security Center (NCSC) of Switzerland for reporting this issue, and to TYPO3 core & security team member Benjamin Franzke for fixing it.

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 12.0.0 before 12.4.31

Fixed in 12.4.31

32 explicitly affected versions

v12.3.0, v12.4.0, v12.4.1, v12.4.10, v12.4.11, v12.4.12, v12.4.13, v12.4.14, v12.4.15, v12.4.16, v12.4.17, v12.4.18, v12.4.19, v12.4.2, v12.4.20, v12.4.21, v12.4.22, v12.4.23, v12.4.24, v12.4.25, v12.4.26, v12.4.27, v12.4.28, v12.4.29, v12.4.3, v12.4.30, v12.4.4, v12.4.5, v12.4.6, v12.4.7, v12.4.8, v12.4.9

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "12.0.0"
        },
        {
          "fixed": "12.4.31"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "v12.3.0",
    "v12.4.0",
    "v12.4.1",
    "v12.4.10",
    "v12.4.11",
    "v12.4.12",
    "v12.4.13",
    "v12.4.14",
    "v12.4.15",
    "v12.4.16",
    "v12.4.17",
    "v12.4.18",
    "v12.4.19",
    "v12.4.2",
    "v12.4.20",
    "v12.4.21",
    "v12.4.22",
    "v12.4.23",
    "v12.4.24",
    "v12.4.25",
    "v12.4.26",
    "v12.4.27",
    "v12.4.28",
    "v12.4.29",
    "v12.4.3",
    "v12.4.30",
    "v12.4.4",
    "v12.4.5",
    "v12.4.6",
    "v12.4.7",
    "v12.4.8",
    "v12.4.9"
  ]
}
Ecosystem versions

From 13.0.0 before 13.4.12

Fixed in 13.4.12

19 explicitly affected versions

v13.0.0, v13.0.1, v13.1.0, v13.1.1, v13.2.1, v13.3.0, v13.3.1, v13.4.0, v13.4.1, v13.4.10, v13.4.11, v13.4.2, v13.4.3, v13.4.4, v13.4.5, v13.4.6, v13.4.7, v13.4.8, v13.4.9

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "13.0.0"
        },
        {
          "fixed": "13.4.12"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "v13.0.0",
    "v13.0.1",
    "v13.1.0",
    "v13.1.1",
    "v13.2.1",
    "v13.3.0",
    "v13.3.1",
    "v13.4.0",
    "v13.4.1",
    "v13.4.10",
    "v13.4.11",
    "v13.4.2",
    "v13.4.3",
    "v13.4.4",
    "v13.4.5",
    "v13.4.6",
    "v13.4.7",
    "v13.4.8",
    "v13.4.9"
  ]
}

References