TYPO3 CMS Webhooks Server Side Request Forgery

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

3.3 · CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:L

EPSS

• CVE-2025-47936: 0.27% estimated exploitation activity in the next 30 days; percentile 19.64 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

20 May 2025, 19:20 UTC

Last modified by the source

20 May 2025, 19:20 UTC

Source last checked

26 Oct 2026, 14:33 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-p4xx-m758-3hpx

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-47936

Advisory: TYPO3 CMS Webhooks Server Side Request Forgery
IDs: CVE-2025-47936, GHSA-p4xx-m758-3hpx
Record: https://patchnext.com/advisories/cve-2025-47936 (revision 1, source checked 26 Oct 2026, 14:33 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: typo3/cms-webhooks 13.4.12, 12.4.31. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist typo3/cms-webhooks: affected >= 12.0.0, <= 12.4.30; >= 13.0.0, <= 13.4.11; fixed in 13.4.12, 12.4.31

## Suggested inspection (read-only)
- Packagist typo3/cms-webhooks: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on typo3/cms-webhooks.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-p4xx-m758-3hpx (GitHub-reviewed advisory GHSA-p4xx-m758-3hpx lists affected ranges: Packagist typo3/cms-webhooks >=12.0.0 =13.0.0 <=13.4.11)

Commands are suggestions: review each one before running it.