CVE-2025-47936: TYPO3 Vulnerable to Server Side Request Forgery via Webhooks

Published May 20, 2025
·
Updated

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 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.

Other sources

TYPO3 is an open source, PHP based web content management system. In versions on the 12.x branch prior to 12.4.31 LTS and the 13.x branch prior to 13.4.2 LTS, Webhooks are inherently vulnerable to Cross-Site Request Forgery (CSRF), 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. Users should update to TYPO3 version 12.4.31 LTS or 13.4.12 LTS to fix the problem.

NVD

Affected Software

5 affected componentsFixes available
Typo3 TYPO3<12.4.31, <13.4.2
composer/typo3/cms-webhooks>=13.0.0<=13.4.11
13.4.12
composer/typo3/cms-webhooks>=12.0.0<=12.4.30
12.4.31
Typo3 TYPO3>=12.0.0<12.4.31
Typo3 TYPO3>=13.0.0<13.4.12

Event History

May 20, 2025
CVE Published
via MITRE·01:23 PM
Data Sourced
via MITRE·01:23 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:15 PM
Affected Software
Advisory Published
via GitHub·07:20 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-47936?

CVE-2025-47936 is classified as a high severity vulnerability due to the risk of Cross-Site Request Forgery (CSRF) attacks affecting user data.

2

How do I fix CVE-2025-47936?

To mitigate CVE-2025-47936, upgrade TYPO3 to version 12.4.31 LTS or 13.4.2 LTS or later.

3

What versions of TYPO3 are affected by CVE-2025-47936?

CVE-2025-47936 affects TYPO3 versions prior to version 12.4.31 LTS and 13.4.2 LTS.

4

What type of vulnerability is CVE-2025-47936?

CVE-2025-47936 is a Cross-Site Request Forgery (CSRF) vulnerability.

5

Who is impacted by CVE-2025-47936?

Any TYPO3 user running affected versions may be vulnerable to exploitation through CVE-2025-47936.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203