CVE-2025-47936 is a low-severity (CVSS 3.3) Server-Side Request Forgery (SSRF) vulnerability in typo3/cms-webhooks. A fix is available for typo3/cms-webhooks — see the affected versions and patch details below.
TYPO3 Vulnerable to Server Side Request Forgery via Webhooks
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-47936.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
typo3/cms-webhooks🐘typo3/cms-webhooksReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
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 emptyarray, 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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/cms-webhooks | ≥ 12.0.0&&< 12.4.31 | 12.4.31composer require typo3/cms-webhooks:^12.4.31 |
| 🐘Packagist | typo3/cms-webhooks | ≥ 13.0.0&&< 13.4.12 | 13.4.12composer require typo3/cms-webhooks:^13.4.12 |
Affected Products
typo3typo3Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-webhooks, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/cms-webhooks to 12.4.31 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-47936 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.
Frequently Asked Questions
Is CVE-2025-47936 in your dependencies?
Find it across Packagist, including transitive dependencies.