Server-side Request Forgery (SSRF) Affecting craftcms/cms package, versions >=3.5.0, <4.16.17>=5.0.0-RC1, <5.8.21
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-14873637
- published13 Jan 2026
- disclosed5 Jan 2026
- creditHesham
Introduced: 5 Jan 2026
CVE-2025-68437 (opens in a new tab)How to fix?
Upgrade craftcms/cms to version 4.16.17, 5.8.21 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 save_<VolumeName>_Asset mutation's _file input, specifically the url parameter. An attacker can access internal network resources, bypass firewall rules, and exfiltrate sensitive data by providing URLs that point to internal services or cloud metadata endpoints, causing the server to fetch and store their content as assets.
Note: This is only exploitable if the attacker has GraphQL permissions to edit and create assets in the targeted volume.