CVE-2025-68437: CWE-918: Server-Side Request Forgery (SSRF) in craftcms cms
Craft is a platform for creating digital experiences. In versions 5.0.0-RC1 through 5.8.20 and 4.0.0-RC1 through 4.16.16, the Craft CMS GraphQL `save_<VolumeName>_Asset` mutation is vulnerable to Server-Side Request Forgery (SSRF). This vulnerability arises because the `_file` input, specifically its `url` parameter, allows the server to fetch content from arbitrary remote locations without proper validation. Attackers can exploit this by providing internal IP addresses or cloud metadata endpoints as the `url`, forcing the server to make requests to these restricted services. The fetched content is then saved as an asset, which can subsequently be accessed and exfiltrated, leading to potential data exposure and infrastructure compromise. This exploitation requires specific GraphQL permissions for asset management within the targeted volume. Users should update to the patched 5.8.21 and 4.16.17 releases to mitigate the issue.
AI Analysis
Technical Summary
CVE-2025-68437 is a Server-Side Request Forgery (SSRF) vulnerability identified in Craft CMS, a popular content management system used for building digital experiences. The vulnerability exists in the GraphQL API, specifically in the `save_<VolumeName>_Asset` mutation, which accepts a `_file` input containing a `url` parameter. Due to insufficient validation of this URL parameter, an attacker with appropriate GraphQL permissions related to asset management can supply arbitrary URLs, including internal IP addresses or cloud provider metadata service endpoints. When exploited, the server fetches the content from these URLs and saves it as an asset within the CMS. This behavior allows attackers to access internal resources that are normally inaccessible externally, such as internal services or sensitive metadata endpoints, potentially leading to information disclosure or further infrastructure compromise. The vulnerability affects Craft CMS versions from 4.0.0-RC1 up to but not including 4.16.17, and 5.0.0-RC1 up to but not including 5.8.21. Exploitation requires authenticated users with high privileges (GraphQL permissions for asset management), and no user interaction is needed beyond this. The CVSS 4.0 score is 5.0 (medium severity), reflecting network attack vector, low attack complexity, and the need for privileges. No known exploits are currently reported in the wild. The recommended mitigation is to upgrade to the patched versions 4.16.17 or 5.8.21, which include proper validation to prevent SSRF attacks via the GraphQL API.
Potential Impact
For European organizations, this SSRF vulnerability poses a significant risk, especially for those relying on Craft CMS for their web presence or digital platforms. Exploitation could allow attackers to bypass perimeter defenses and access internal network resources, including sensitive internal services and cloud metadata endpoints that may contain credentials or configuration data. This can lead to unauthorized data exposure, lateral movement within the network, and potential compromise of other infrastructure components. Organizations in sectors with strict data protection regulations, such as finance, healthcare, and government, could face compliance violations and reputational damage if sensitive data is leaked. Additionally, the ability to save fetched content as assets may facilitate persistent data exfiltration channels or staging points for further attacks. Since exploitation requires authenticated users with high privileges, insider threats or compromised accounts pose a particular concern. The medium severity rating suggests a moderate but non-trivial risk that should be addressed promptly to prevent escalation.
Mitigation Recommendations
European organizations should immediately verify if their Craft CMS installations fall within the affected version ranges and prioritize upgrading to versions 4.16.17 or 5.8.21 where the vulnerability is patched. Beyond patching, organizations should audit GraphQL permissions to ensure only trusted users have asset management capabilities, minimizing the risk of privilege abuse. Implement network segmentation and firewall rules to restrict the CMS server's ability to initiate outbound requests to internal IP ranges and cloud metadata endpoints, thereby limiting SSRF impact. Employ monitoring and alerting on unusual GraphQL mutation activity or asset creation patterns that could indicate exploitation attempts. Conduct regular reviews of user accounts and enforce strong authentication mechanisms to reduce the risk of compromised credentials. Finally, consider deploying Web Application Firewalls (WAFs) with SSRF detection capabilities tailored to Craft CMS traffic patterns to provide an additional layer of defense.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Italy, Spain, Poland
CVE-2025-68437: CWE-918: Server-Side Request Forgery (SSRF) in craftcms cms
Description
Craft is a platform for creating digital experiences. In versions 5.0.0-RC1 through 5.8.20 and 4.0.0-RC1 through 4.16.16, the Craft CMS GraphQL `save_<VolumeName>_Asset` mutation is vulnerable to Server-Side Request Forgery (SSRF). This vulnerability arises because the `_file` input, specifically its `url` parameter, allows the server to fetch content from arbitrary remote locations without proper validation. Attackers can exploit this by providing internal IP addresses or cloud metadata endpoints as the `url`, forcing the server to make requests to these restricted services. The fetched content is then saved as an asset, which can subsequently be accessed and exfiltrated, leading to potential data exposure and infrastructure compromise. This exploitation requires specific GraphQL permissions for asset management within the targeted volume. Users should update to the patched 5.8.21 and 4.16.17 releases to mitigate the issue.
AI-Powered Analysis
Technical Analysis
CVE-2025-68437 is a Server-Side Request Forgery (SSRF) vulnerability identified in Craft CMS, a popular content management system used for building digital experiences. The vulnerability exists in the GraphQL API, specifically in the `save_<VolumeName>_Asset` mutation, which accepts a `_file` input containing a `url` parameter. Due to insufficient validation of this URL parameter, an attacker with appropriate GraphQL permissions related to asset management can supply arbitrary URLs, including internal IP addresses or cloud provider metadata service endpoints. When exploited, the server fetches the content from these URLs and saves it as an asset within the CMS. This behavior allows attackers to access internal resources that are normally inaccessible externally, such as internal services or sensitive metadata endpoints, potentially leading to information disclosure or further infrastructure compromise. The vulnerability affects Craft CMS versions from 4.0.0-RC1 up to but not including 4.16.17, and 5.0.0-RC1 up to but not including 5.8.21. Exploitation requires authenticated users with high privileges (GraphQL permissions for asset management), and no user interaction is needed beyond this. The CVSS 4.0 score is 5.0 (medium severity), reflecting network attack vector, low attack complexity, and the need for privileges. No known exploits are currently reported in the wild. The recommended mitigation is to upgrade to the patched versions 4.16.17 or 5.8.21, which include proper validation to prevent SSRF attacks via the GraphQL API.
Potential Impact
For European organizations, this SSRF vulnerability poses a significant risk, especially for those relying on Craft CMS for their web presence or digital platforms. Exploitation could allow attackers to bypass perimeter defenses and access internal network resources, including sensitive internal services and cloud metadata endpoints that may contain credentials or configuration data. This can lead to unauthorized data exposure, lateral movement within the network, and potential compromise of other infrastructure components. Organizations in sectors with strict data protection regulations, such as finance, healthcare, and government, could face compliance violations and reputational damage if sensitive data is leaked. Additionally, the ability to save fetched content as assets may facilitate persistent data exfiltration channels or staging points for further attacks. Since exploitation requires authenticated users with high privileges, insider threats or compromised accounts pose a particular concern. The medium severity rating suggests a moderate but non-trivial risk that should be addressed promptly to prevent escalation.
Mitigation Recommendations
European organizations should immediately verify if their Craft CMS installations fall within the affected version ranges and prioritize upgrading to versions 4.16.17 or 5.8.21 where the vulnerability is patched. Beyond patching, organizations should audit GraphQL permissions to ensure only trusted users have asset management capabilities, minimizing the risk of privilege abuse. Implement network segmentation and firewall rules to restrict the CMS server's ability to initiate outbound requests to internal IP ranges and cloud metadata endpoints, thereby limiting SSRF impact. Employ monitoring and alerting on unusual GraphQL mutation activity or asset creation patterns that could indicate exploitation attempts. Conduct regular reviews of user accounts and enforce strong authentication mechanisms to reduce the risk of compromised credentials. Finally, consider deploying Web Application Firewalls (WAFs) with SSRF detection capabilities tailored to Craft CMS traffic patterns to provide an additional layer of defense.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2025-12-17T15:43:01.352Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 695c36383839e44175942ebe
Added to database: 1/5/2026, 10:07:52 PM
Last enriched: 1/5/2026, 10:22:41 PM
Last updated: 1/8/2026, 2:27:22 PM
Views: 15
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-21895: CWE-703: Improper Check or Handling of Exceptional Conditions in RustCrypto RSA
LowCVE-2025-8307: CWE-257 Storing Passwords in a Recoverable Format in Asseco InfoMedica Plus
MediumCVE-2025-8306: CWE-1220 Insufficient Granularity of Access Control in Asseco InfoMedica Plus
MediumCVE-2025-14025: Incorrect Execution-Assigned Permissions in Red Hat Red Hat Ansible Automation Platform 2
HighCVE-2026-21891: CWE-287: Improper Authentication in IceWhaleTech ZimaOS
CriticalActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.