craftcms/cms
Affected
- introduced
5.0.0-RC1, fixed5.8.21(ecosystem)
Fixed versions
5.8.21
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2025-68437
Craft CMS vulnerable to Server-Side Request Forgery (SSRF) via GraphQL Asset Upload Mutation
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.
References:
https://github.com/craftcms/cms/commit/013db636fdb38f3ce5657fd196b6d952f98ebc52
https://github.com/craftcms/cms/blob/5.x/CHANGELOG.md#5821---2025-12-04
---
Required Permissions
The exploitation requires a few permissions to be enabled in the used GraphQL schema:
<VolumeName> volume"<VolumeName> volume"Steps to Reproduce
http://craft.local/admin/graphiql & set the created schema.<VolumeName> with your volume name)*:mutation {
save_<VolumeName>_Asset(_file: {
url: "http://127.0.0.1:80/index.php"
filename: "poc.txt"
}) {
id
}
}
index.php response will be saved as poc.txt & its content will be accessible via the asset preview/download functionality.http://127.0.0.1:80/index.php was used as an example. However, the url parameter can be leveraged to target internal services, cloud metadata endpoints, or any arbitrary external URL.Impact
Successful exploitation of this SSRF vulnerability allows attackers to access internal network resources, bypass firewall rules, and conduct network reconnaissance.
In cloud environments (AWS, GCP, Azure), this can lead to the theft of sensitive credentials (e.g., IAM roles, service account tokens) from metadata endpoints, potentially resulting in the full compromise of the underlying infrastructure and the exfiltration of sensitive data.
---
Users should update to the patched versions (5.8.21 and 4.16.17) to mitigate the issue.
Users running Craft 3.5.0+ should update to the latest Craft 4.16.17 or 5.8.21 releases.
Medium Basis: The source's own band: MODERATE
5.0.0-RC1, fixed 5.8.21 (ecosystem)5.8.21
The export has no generic command for this ecosystem.
3.5.0, fixed 4.16.17 (ecosystem)4.16.17
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0