CVE-2026-31317
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCraftql v1.3.7 and before is vulnerable to Server-Side Request Forgery (SSRF) which allows an attacker to execute arbitrary code via the vendor/markhuot/craftql/src/Listeners/GetAssetsFieldSchema.php file
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCraftQL v1.3.7 and earlier contains an SSRF vulnerability in the GetAssetsFieldSchema.php file that allows an attacker to induce the server to make arbitrary HTTP requests to internal or external resources, potentially exposing internal services or facilitating further attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify CraftQL installationCheck your Craft CMS plugins directory or composer.json for the presence of the craftql package. Common paths include /vendor/craftcms/craftql/ or check composer.lock for craftql entry.Affected if CraftQL plugin is present in the installation
-
Determine CraftQL versionCheck the installed CraftQL version via composer.json, composer.lock, or the Craft CMS plugin store. Compare the version number against v1.3.7 - versions 1.3.7 and earlier are affected.Affected if Installed version is 1.3.7 or earlier
-
Locate vulnerable fileSearch for the GetAssetsFieldSchema.php file in the CraftQL source code. In a typical installation, this would be at /vendor/craftcms/craftql/src/fields/GetAssetsFieldSchema.php or similar path under the craftql package directory.Affected if GetAssetsFieldSchema.php exists in the CraftQL plugin directory
-
Check if GraphQL field is exposedVerify that the GraphQL API endpoint is accessible and that asset-related GraphQL queries can be executed. The SSRF vulnerability in GetAssetsFieldSchema.php is triggered through GraphQL field schema generation.Affected if GraphQL API is enabled and asset field queries are accessible without additional authentication beyond standard Craft CMS user authentication
A user is affected if CraftQL v1.3.7 or earlier is installed, the GetAssetsFieldSchema.php file is present, and the GraphQL API with asset field capabilities is enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a patched version of CraftQL; if unavailable, implement strict URL validation and network segmentation to prevent the affected code from making unauthorized requests.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-31317 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-31317 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data