Server-side Request Forgery (SSRF) Affecting craftcms/cms package, versions >=3.5.0, <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-15265440
- published11 Feb 2026
- disclosed9 Feb 2026
- creditLeftenantZero
Introduced: 9 Feb 2026
CVE-2026-25492 (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) in handleUpload(), which is exploitable via the save_images_Asset mutation in the GraphQL API. An attacker can retrieve sensitive internal resources, such as AWS credentials, by supplying a malicious URL that resolves to an internal IP address and specifying a permitted file extension. This is only exploitable if GraphQL access is enabled, the attacker possesses a valid GraphQL token with permission to use the save_images_Asset mutation, and the .txt extension is allowed for uploads (which it is by default).