Server-side Request Forgery (SSRF) Affecting typo3/cms-webhooks package, versions >=12.0.0, <12.4.31>=13.0.0, <13.4.12
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Server-side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-PHP-TYPO3CMSWEBHOOKS-10213897
- published21 May 2025
- disclosed20 May 2025
- creditNational Cyber Security Center (NCSC) of Switzerland
Introduced: 20 May 2025
NewCVE-2025-47936 (opens in a new tab)How to fix?
Upgrade typo3/cms-webhooks to version 12.4.31, 13.4.12 or higher.
Overview
typo3/cms-webhooks is a Handle outgoing Webhooks for TYPO3
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF). An attacker can manipulate internal resources by sending crafted requests from a compromised or malicious external site. This is only exploitable if an administrator-level backend user account is logged in.
Note:
To mitigate potential SSRF risks via webhooks, manual configuration of the allowlist in $GLOBALS['TYPO3_CONF_VARS']['HTTP']['allowed_hosts']['webhooks'] is crucial, as the default allows all requests, while an empty array blocks all, and specific hosts restrict access to trusted destinations only.