CVE-2026-25497
Privilege Escalation in Craft CMS GraphQL Allows Cross-Volume Asset Modification
Publication date: 2026-02-09
Last updated on: 2026-02-19
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| craftcms | craft_cms | 4.0.0 |
| craftcms | craft_cms | 4.0.0 |
| craftcms | craft_cms | 4.0.0 |
| craftcms | craft_cms | 4.0.0 |
| craftcms | craft_cms | 5.0.0 |
| craftcms | craft_cms | 5.0.0 |
| craftcms | craft_cms | From 4.0.0 (exc) to 4.17.0 (exc) |
| craftcms | craft_cms | From 5.0.0 (exc) to 5.9.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-639 | The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Craft CMS's GraphQL API in versions from 4.0.0-RC1 to before 4.17.0-beta.1 and 5.9.0-beta.1. It is a Privilege Escalation issue where an authenticated user with write access to one asset volume can escalate their privileges to modify or transfer assets belonging to other volumes, including restricted or private ones. The problem arises because the saveAsset GraphQL mutation checks authorization against the volume defined in the schema but then fetches the target asset by ID without verifying if the asset actually belongs to the authorized volume. This allows unauthorized cross-volume asset modification and transfer.
How can this vulnerability impact me? :
This vulnerability can allow an attacker who has limited write access to one asset volume to gain unauthorized access to other asset volumes, including restricted or private ones. This means they could modify or transfer assets they should not have access to, potentially leading to data tampering, unauthorized data exposure, or disruption of digital content managed by the platform.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade Craft CMS to version 4.17.0-beta.1 or later, or 5.9.0-beta.1 or later, where the issue is fixed.
Until the upgrade can be applied, restrict write access to asset volumes only to trusted users to minimize the risk of privilege escalation via the GraphQL API.