Craft CMS up to 4.16.17/5.8.21 GraphQL Mutation saveAsset server-side request forgery

Summaryinfo

A vulnerability was found in Craft CMS up to 4.16.17/5.8.21. It has been classified as critical. This impacts the function saveAsset of the component GraphQL Mutation Handler. The manipulation leads to server-side request forgery. This vulnerability is referenced as CVE-2026-25493. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Craft CMS up to 4.16.17/5.8.21. This issue affects the function saveAsset of the component GraphQL Mutation Handler. The manipulation with an unknown input leads to a server-side request forgery vulnerability. Using CWE to declare the problem leads to CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Craft is a platform for creating digital experiences. In Craft versions 4.0.0-RC1 through 4.16.17 and 5.0.0-RC1 through 5.8.21, the saveAsset GraphQL mutation validates the initial URL hostname and resolved IP against a blocklist, but Guzzle follows HTTP redirects by default. An attacker can bypass all SSRF protections by hosting a redirect that points to cloud metadata endpoints or any internal IP addresses. This issue is patched in versions 4.16.18 and 5.8.22.

It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-25493 since 02/02/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 4.16.18 or 5.8.22 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 0974055634af68998f67850ab2045d8aaa19fa98 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Content Management System

Vendor

• Craft

Name

• CMS

Version

• 4.16.0
• 4.16.1
• 4.16.2
• 4.16.3
• 4.16.4
• 4.16.5
• 4.16.6
• 4.16.7
• 4.16.8
• 4.16.9
• 4.16.10
• 4.16.11
• 4.16.12
• 4.16.13
• 4.16.14
• 4.16.15
• 4.16.16
• 4.16.17
• 5.8.0
• 5.8.1
• 5.8.2
• 5.8.3
• 5.8.4
• 5.8.5
• 5.8.6
• 5.8.7
• 5.8.8
• 5.8.9
• 5.8.10
• 5.8.11
• 5.8.12
• 5.8.13
• 5.8.14
• 5.8.15
• 5.8.16
• 5.8.17
• 5.8.18
• 5.8.19
• 5.8.20
• 5.8.21

License

• free

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion