Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Packagist package

typo3/cms-webhooks

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Low, CVSS 3.3PackagistPublished

    TYPO3 CMS Webhooks Server Side Request Forgery

    CVE-2025-47936 · GHSA-p4xx-m758-3hpx

    Affected
    • Packagist typo3/cms-webhooks >= 12.0.0, <= 12.4.30; >= 13.0.0, <= 13.4.11
    Fixed in
    13.4.1212.4.31· Vendor fix available
    Issue
    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['TYPO3CONFVARS']['HTTP']['allowedhosts']['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…

    Recommended action: Upgrade to 13.4.12 or 12.4.31 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →