CVE-2026-25497: CWE-639: Authorization Bypass Through User-Controlled Key in craftcms cms
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.
AI Analysis
Technical Summary
CVE-2026-25497 is a privilege escalation vulnerability identified in the Craft CMS platform, specifically affecting its GraphQL API's saveAsset mutation. Craft CMS is widely used for building digital experiences and managing content. The vulnerability exists in versions from 4.0.0-RC1 up to before 4.17.0-beta.1 and 5.9.0-beta.1. The core issue stems from improper authorization validation: while the mutation checks permissions against the schema-resolved asset volume, it retrieves the target asset by its ID without confirming that the asset belongs to the authorized volume. This discrepancy allows an authenticated user with write permissions on one asset volume to escalate privileges and modify or transfer assets belonging to other volumes, including those marked as restricted or private. This cross-volume authorization bypass violates the principle of least privilege and can lead to unauthorized data exposure or tampering. The vulnerability is classified under CWE-639 (Authorization Bypass Through User-Controlled Key). The CVSS 4.0 base score is 8.6 (high severity), reflecting network exploitability, low attack complexity, no required user interaction, and significant impact on confidentiality and integrity. No known exploits are reported in the wild as of the publication date. The issue is resolved in Craft CMS versions 4.17.0-beta.1 and 5.9.0-beta.1, where proper asset ownership verification is enforced during the saveAsset mutation.
Potential Impact
For European organizations using affected versions of Craft CMS, this vulnerability poses a significant risk to the confidentiality and integrity of digital assets managed within the CMS. Attackers with authenticated write access to any asset volume can manipulate or transfer assets from other volumes, potentially exposing sensitive or restricted content. This can lead to unauthorized data disclosure, content defacement, intellectual property theft, or disruption of digital services. Organizations in sectors such as media, e-commerce, government, and education that rely on Craft CMS for content management are particularly at risk. The ability to escalate privileges within the CMS can also facilitate further lateral movement or compromise within the organization's digital infrastructure. Given the network-exploitable nature and lack of required user interaction, the vulnerability could be exploited remotely by insiders or compromised accounts, increasing the threat surface. Failure to patch may result in reputational damage, regulatory non-compliance (e.g., GDPR breaches due to unauthorized data access), and financial losses.
Mitigation Recommendations
European organizations should immediately assess their Craft CMS deployments to identify affected versions (>= 4.0.0-RC1 and < 4.17.0-beta.1, and >= 5.0.0-RC1 and < 5.8.22). The primary mitigation is to upgrade to Craft CMS versions 4.17.0-beta.1 or later, or 5.9.0-beta.1 or later, where the vulnerability is patched. Until upgrades are applied, organizations should restrict write access to asset volumes to only trusted and necessary users, enforce strong authentication and account monitoring to detect suspicious activity, and consider implementing additional application-layer access controls or Web Application Firewall (WAF) rules to monitor and block suspicious GraphQL mutation requests. Regularly audit asset volume permissions and logs for unauthorized modifications. Additionally, organizations should review their incident response plans to quickly address potential exploitation and data breaches related to this vulnerability. Coordination with CMS administrators and developers is critical to ensure timely patching and configuration hardening.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Italy, Spain, Poland
CVE-2026-25497: CWE-639: Authorization Bypass Through User-Controlled Key in craftcms cms
Description
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.
AI-Powered Analysis
Technical Analysis
CVE-2026-25497 is a privilege escalation vulnerability identified in the Craft CMS platform, specifically affecting its GraphQL API's saveAsset mutation. Craft CMS is widely used for building digital experiences and managing content. The vulnerability exists in versions from 4.0.0-RC1 up to before 4.17.0-beta.1 and 5.9.0-beta.1. The core issue stems from improper authorization validation: while the mutation checks permissions against the schema-resolved asset volume, it retrieves the target asset by its ID without confirming that the asset belongs to the authorized volume. This discrepancy allows an authenticated user with write permissions on one asset volume to escalate privileges and modify or transfer assets belonging to other volumes, including those marked as restricted or private. This cross-volume authorization bypass violates the principle of least privilege and can lead to unauthorized data exposure or tampering. The vulnerability is classified under CWE-639 (Authorization Bypass Through User-Controlled Key). The CVSS 4.0 base score is 8.6 (high severity), reflecting network exploitability, low attack complexity, no required user interaction, and significant impact on confidentiality and integrity. No known exploits are reported in the wild as of the publication date. The issue is resolved in Craft CMS versions 4.17.0-beta.1 and 5.9.0-beta.1, where proper asset ownership verification is enforced during the saveAsset mutation.
Potential Impact
For European organizations using affected versions of Craft CMS, this vulnerability poses a significant risk to the confidentiality and integrity of digital assets managed within the CMS. Attackers with authenticated write access to any asset volume can manipulate or transfer assets from other volumes, potentially exposing sensitive or restricted content. This can lead to unauthorized data disclosure, content defacement, intellectual property theft, or disruption of digital services. Organizations in sectors such as media, e-commerce, government, and education that rely on Craft CMS for content management are particularly at risk. The ability to escalate privileges within the CMS can also facilitate further lateral movement or compromise within the organization's digital infrastructure. Given the network-exploitable nature and lack of required user interaction, the vulnerability could be exploited remotely by insiders or compromised accounts, increasing the threat surface. Failure to patch may result in reputational damage, regulatory non-compliance (e.g., GDPR breaches due to unauthorized data access), and financial losses.
Mitigation Recommendations
European organizations should immediately assess their Craft CMS deployments to identify affected versions (>= 4.0.0-RC1 and < 4.17.0-beta.1, and >= 5.0.0-RC1 and < 5.8.22). The primary mitigation is to upgrade to Craft CMS versions 4.17.0-beta.1 or later, or 5.9.0-beta.1 or later, where the vulnerability is patched. Until upgrades are applied, organizations should restrict write access to asset volumes to only trusted and necessary users, enforce strong authentication and account monitoring to detect suspicious activity, and consider implementing additional application-layer access controls or Web Application Firewall (WAF) rules to monitor and block suspicious GraphQL mutation requests. Regularly audit asset volume permissions and logs for unauthorized modifications. Additionally, organizations should review their incident response plans to quickly address potential exploitation and data breaches related to this vulnerability. Coordination with CMS administrators and developers is critical to ensure timely patching and configuration hardening.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-02-02T16:31:35.824Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 698a3d0c4b57a58fa16d39e6
Added to database: 2/9/2026, 8:01:16 PM
Last enriched: 2/9/2026, 8:15:35 PM
Last updated: 2/9/2026, 10:28:17 PM
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-25925: CWE-502: Deserialization of Untrusted Data in modery PowerDocu
HighCVE-2026-25923: CWE-434: Unrestricted Upload of File with Dangerous Type in My-Little-Forum mylittleforum
HighCVE-2026-25808: CWE-862: Missing Authorization in fedify-dev hollo
HighCVE-2026-25807: CWE-94: Improper Control of Generation of Code ('Code Injection') in TaklaXBR zai-shell
HighCVE-2025-15317: Allocation of Resources Without Limits or Throttling in Tanium Tanium Server
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.