Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-68437: CWE-918: Server-Side Request Forgery (SSRF) in craftcms cms

0
Medium
VulnerabilityCVE-2025-68437cvecve-2025-68437cwe-918
Published: Mon Jan 05 2026 (01/05/2026, 21:52:29 UTC)
Source: CVE Database V5
Vendor/Project: craftcms
Product: cms

Description

CVE-2025-68437 is a Server-Side Request Forgery (SSRF) vulnerability in Craft CMS versions 4. 0. 0-RC1 through 4. 16. 16 and 5. 0. 0-RC1 through 5. 8. 20. It affects the GraphQL mutation `save_<VolumeName>_Asset` where the `_file` input's `url` parameter is not properly validated, allowing attackers to make the server fetch arbitrary remote resources.

AI-Powered Analysis

AILast updated: 01/13/2026, 00:59:14 UTC

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 flaw exists in the GraphQL API, specifically within the `save_<VolumeName>_Asset` mutation, which accepts a `_file` input containing a `url` parameter. This parameter is intended to allow the server to fetch and save remote assets. However, due to insufficient validation of the URL input, an attacker with appropriate GraphQL permissions can supply URLs pointing to internal IP addresses or cloud provider metadata endpoints. This forces the server to make unauthorized requests to internal services that are typically inaccessible externally. The fetched content is then saved as an asset within the CMS, which the attacker can subsequently access and exfiltrate. This can lead to exposure of sensitive internal information, such as cloud instance metadata, credentials, or other internal network resources. 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 elevated GraphQL permissions related to asset management, which limits the attack surface to users or roles with such privileges. The CVSS 4.0 vector indicates network attack vector, low attack complexity, partial privileges required, no user interaction, and high impact on confidentiality. No public exploits have been reported yet, but the vulnerability poses a significant risk if leveraged in targeted attacks. The recommended mitigation is to update Craft CMS to versions 4.16.17 or 5.8.21 where the issue has been patched.

Potential Impact

For European organizations using Craft CMS, this SSRF vulnerability can have several impacts. If exploited, attackers could access internal network resources, including cloud metadata services, potentially leading to credential theft and lateral movement within the infrastructure. This can result in data breaches, unauthorized access to sensitive information, and disruption of services. Organizations in sectors with strict data protection regulations (e.g., GDPR) face increased compliance risks and potential fines if sensitive data is exposed. The requirement for specific GraphQL permissions somewhat limits the risk to insiders or compromised accounts with asset management rights, but privilege escalation or phishing could enable such access. Additionally, the ability to exfiltrate internal data via saved assets can facilitate further attacks or espionage. The medium CVSS score reflects moderate risk, but the potential for significant damage exists if combined with other vulnerabilities or misconfigurations. European organizations relying on Craft CMS for public-facing or internal digital platforms should prioritize patching to prevent exploitation.

Mitigation Recommendations

1. Upgrade Craft CMS installations to version 5.8.21 or 4.16.17 immediately to apply the official patch addressing the SSRF vulnerability. 2. Review and restrict GraphQL permissions, ensuring only trusted users have asset management rights, minimizing the attack surface. 3. Implement network segmentation and firewall rules to limit the CMS server's ability to access internal IP ranges and cloud metadata endpoints, reducing SSRF impact. 4. Monitor GraphQL API usage logs for unusual asset save requests or unexpected URL parameters that may indicate exploitation attempts. 5. Employ Web Application Firewalls (WAFs) with custom rules to detect and block SSRF patterns targeting internal resources. 6. Conduct regular security audits and penetration tests focusing on API endpoints and permission configurations. 7. Educate developers and administrators about SSRF risks and secure coding practices related to URL input validation.

Need more detailed analysis?Upgrade to Pro Console

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/13/2026, 12:59:14 AM

Last updated: 2/4/2026, 1:28:18 PM

Views: 39

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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.

Latest Threats