CVE-2026-72784 in Craft CMS
Summary
by MITRE • 08/11/2026
Craft CMS versions >= 5.0.0-RC1 before 5.10.6 and >= 4.0.0-RC1 before 4.18.2 contain a server-side request forgery vulnerability in the GraphQL save<Volume>Asset mutation, which fetches an attacker-supplied URL server-side. The anti-SSRF validation is incomplete: validateIp() does not cover CGNAT (100.64.0.0/10) or NAT64 (64:ff9b::/96) ranges, and the only IP check runs after the request has already been issued. An attacker holding a GraphQL token scoped only to asset-creation permissions can disclose internal HTTP content from CGNAT/NAT64 targets, force outbound GET requests to internal hosts (including RFC1918, loopback, and metadata endpoints), and enumerate internal services.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 08/11/2026
This vulnerability exists within Craft CMS versions prior to specific patch releases, affecting both the 4.x and 5.x branches with significant security implications for server-side operations. The flaw resides in the GraphQL save<Volume>Asset mutation which processes attacker-controlled URLs through server-side HTTP requests without adequate protection against server-side request forgery attacks.
The technical implementation of this vulnerability stems from incomplete SSRF validation mechanisms within the Craft CMS framework. Specifically, the validateIp() function fails to properly address CGNAT (Classless Inter-Domain Routing) ranges spanning 100.64.0.0/10 and NAT64 (IPv6-to-IPv4 translation) ranges defined as 64:ff9b::/96. These network ranges are commonly used in modern networking environments for address translation and internal service access, yet the validation logic does not account for their existence. Additionally, the IP address verification occurs after the HTTP request has already been initiated, allowing malicious requests to proceed regardless of the validation outcome.
The operational impact of this vulnerability is substantial for organizations utilizing Craft CMS with GraphQL APIs enabled. An attacker with a GraphQL token possessing only asset-creation permissions can exploit this weakness to access internal HTTP services that would normally be restricted from external exposure. This includes enumeration of internal network services, disclosure of sensitive content hosted on internal servers, and forced outbound GET requests to RFC1918 private address ranges, loopback interfaces, and metadata endpoints such as AWS instance metadata services or Azure Instance Metadata Service. The vulnerability effectively bypasses network segmentation controls by leveraging the legitimate asset upload functionality to probe internal systems.
This vulnerability aligns with CWE-918 (Server-Side Request Forgery) and maps to ATT&CK technique T1071.004 (Application Layer Protocol: DNS) and T1566.002 (Phishing: Spearphishing Attachment). Organizations should immediately apply patches to Craft CMS versions 4.18.2 and 5.10.6 or later, which address the incomplete SSRF validation by implementing comprehensive IP range checking that includes CGNAT and NAT64 ranges. Additional mitigations include restricting GraphQL endpoints from internal network access, implementing network-level firewalls to block outbound requests to private address ranges, and conducting thorough security reviews of all mutation operations that handle external URLs. The vulnerability demonstrates the critical importance of validating network addresses at the earliest possible stage in request processing and highlights the necessity of considering modern networking paradigms such as CGNAT and NAT64 in security validation mechanisms.