Server-side Request Forgery (SSRF) Affecting craftcms/cms package, versions >=4.0.0-RC1, <4.16.18>=5.0.0-RC1, <5.8.22
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
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-CRAFTCMSCMS-15268423
- published12 Feb 2026
- disclosed9 Feb 2026
- creditmHe4am
Introduced: 9 Feb 2026
CVE-2026-25493 (opens in a new tab)How to fix?
Upgrade craftcms/cms to version 4.16.18, 5.8.22 or higher.
Overview
craftcms/cms is a content management system.
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the saveAsset GraphQL mutation validates the initial URL hostname and resolved IP against a blocklis. An attacker can access internal resources or sensitive cloud metadata by submitting a URL that triggers an HTTP redirect to internal IP addresses or cloud metadata endpoints.
Note: This is possible because the initial hostname and IP validation can be bypassed when HTTP redirects are followed by the underlying HTTP client.
Workaround
This vulnerability can be mitigated by disabling HTTP redirects.