CVE-2026-25497: Craft has a GraphQL Asset Mutation Privilege Escalation
Noroxi assessment
Priority: Monitor (action score 34/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.47% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: craftcms cms 4.17.0-beta.1.
Low priority for now. Upgrade to craftcms cms 4.17.0-beta.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Craft is a platform for creating digital experiences. In Craft versions from 4.0.0-RC1 to before 4.17.0-beta.1 and 5.9.0-beta.1, there is a Privilege Escalation vulnerability in Craft CMS’s GraphQL API that allows an authenticated user with write access to one asset volume to escalate their privileges and modify/transfer assets belonging to any other volume, including restricted or private volumes to which they should not have access. The saveAsset GraphQL mutation validates authorization against the schema-resolved volume but fetches the target asset by ID without verifying that the asset belongs to the authorized volume. This allows unauthorized cross-volume asset modification and transfer. This vulnerability is fixed in 4.17.0-beta.1 and 5.9.0-beta.1.
- Published
- Feb 9, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 41th percentile
- CWE
- CWE-639
Report tools
Action score
34
Low priority for now.
- CVSS
- 34 / 40 · 8.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 8.6
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| craftcms | craft cms | cpe:2.3:a:craftcms:craft_cms |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
craftcms cms
- >= 5.0.0-RC1, < 5.8.22, >= 4.0.0-RC1, < 4.17.0-beta.1affected
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- craftcms craft cmsafter 4.0.0 · before 4.17.0
- craftcms craft cmsafter 5.0.0 · before 5.9.0
- craftcms craft cms4.0.0
- craftcms craft cms5.0.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Packagist | craftcms/cms | from 4.0.0-RC1 · before 4.17.0-beta.1 | 4.17.0-beta.1 |
| Packagist | craftcms/cms | from 5.0.0-RC1 · before 5.9.0-beta.1 | 5.9.0-beta.1 |
Same product
craftcms: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-32432Craft CMS Allows Remote Code ExecutionKEV100Now
- CVE-2024-56145RCE when PHP `register_argc_argv` config setting is enabled in craftcms/cmsKEV96Now
- CVE-2025-23209Potential RCE with a compromised security key in craft/cmsKEV68This week
Published before and after this one in the same product
- ← EarlierCVE-2026-25495Feb 9, 2026 · Craft has a SQL Injection in Element Indexes via criteria[orderBy]34Monitor
- ← EarlierCVE-2026-25496Feb 9, 2026 · Craft has a stored XSS in Number Prefix & Suffix Fields19Monitor
- Later →CVE-2026-25498Feb 9, 2026 · Craft has a potential authenticated Remote Code Execution via malicious attached Behavior34Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| craftcms cms | 4.17.0-beta.1 · description | Vendor (CNA) |
| Packagist:craftcms/cms | 4.17.0-beta.1 | Package registry (OSV) |
| Packagist:craftcms/cms | 5.9.0-beta.1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-2869623 days apartCraft affected by IDOR via GraphQL @parseRefs34Monitor
- CVE-2026-2878123 days apartCraft Affected by Entries Authorship Spoofing via Mass Assignment28Monitor
- CVE-2026-2906923 days apartCraft has an unauthenticated activation email trigger with potential user enumeration27Monitor
- CVE-2026-2878223 days apartCraft has a Permission Bypass and IDOR in Duplicate Entry Action21Monitor
- CVE-2026-3315843 days apartCraft CMS: Low-privilege users could read private asset contents when editing an asset (IDOR)19Monitor
- CVE-2026-3316043 days apartCraft CMS: Anonymous "generate transform" calls for assets can expose private assets via transform URL10Monitor
Not on record for this CVE: EPSS history · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-639 · Authorization Bypass Through User-Controlled KeyCVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Root cause
The endpoint fetches the record by the ID sent in the request, but never checks whether the record belongs to the requesting user.
The bug in code
The whole CWE-639 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const invoice = await Invoice.findById(req.params.id);
res.json(invoice);Fixed
const invoice = await Invoice.findOne({
id: req.params.id,
ownerId: req.user.id,
});
if (!invoice) return res.sendStatus(404);
res.json(invoice);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.