VulnerabilityPublished 9 Feb 2026

CVE-2026-25497: craftcms cms · Insecure Direct Object Reference

Affects craftcms cmsSource CVE Database V5

Not known to be exploited · CVSS 8.6 High : upgrade to 5.8.22 or 4.17.0-beta.1 soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score

8.6High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 5.8.22, 4.17.0-beta.1

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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: High
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the vulnerable system. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the vulnerable system.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade craftcms cms to 5.8.22 or 4.17.0-beta.1.

Affected software

Product	Affected	Fixed in
craftcmscms	Affected >=5.0.0-RC1 <5.8.22	Fixed in 5.8.22
craftcmscms	Affected >=4.0.0-RC1 <4.17.0-beta.1	Fixed in 4.17.0-beta.1

AI-suggested

European organizations should immediately assess their Craft CMS installations to identify affected versions (>=4.0.0-RC1 and <4.17.0-beta.1, >=5.0.0-RC1 and <5.8.22). The primary mitigation is to upgrade Craft CMS to versions 4.17.0-beta.1 or later and 5.9.0-beta.1 or later where the vulnerability is fixed. Until patching is possible, organizations should restrict write access to asset volumes to trusted users only and implement strict monitoring of GraphQL API usage to detect anomalous asset modifications or transfers. Employing Web Application Firewalls (WAFs) with custom rules to detect unusual GraphQL mutation patterns may help mitigate exploitation attempts. Additionally, review and tighten user permissions to enforce the principle of least privilege, ensuring users have access only to necessary asset volumes. Regularly audit asset volume ownership and changes to detect unauthorized modifications. Finally, implement strong authentication mechanisms and monitor for compromised accounts to reduce the risk of insider exploitation.

Description

CVE-2026-25497 is a high-severity privilege escalation vulnerability in Craft CMS versions from 4.0.0-RC1 up to before 4.17.0-beta.1 and 5.9.0-beta.1. It affects the GraphQL API, specifically the saveAsset mutation, allowing an authenticated user with write access to one asset volume to modify or transfer assets in other volumes without proper authorization checks.

Impact

For European organizations using affected Craft CMS versions, this vulnerability poses a substantial risk to the confidentiality and integrity of digital assets managed via the CMS. Unauthorized modification or transfer of assets across volumes can lead to data leakage, defacement, or unauthorized content distribution, potentially damaging brand reputation and violating data protection regulations such as GDPR. Organizations relying on Craft CMS for managing sensitive or restricted content are particularly at risk, as attackers with write access to any asset volume can escalate privileges to access protected assets. This could also facilitate further attacks by manipulating critical assets or injecting malicious content. The vulnerability does not directly affect availability but can indirectly impact business operations through content integrity loss. Given the ease of exploitation by authenticated users without user interaction, insider threats or compromised accounts represent a significant attack vector. The absence of known exploits in the wild suggests limited current exploitation but also highlights the importance of timely patching to prevent future attacks.

CWE-639Authorization Bypass Through User-Controlled Key (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #24OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
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.
Architecture and Design
For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
Architecture and Design · Implementation
Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
Architecture and Design
Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
OWASP Cheat Sheets
Access Control (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V4.1.2 (opens in a new tab)
V4.2.1 (opens in a new tab)
V8.3.8 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Feb 2026, 09:45 UTC

WeaknessesCWE-639

Technical details

References

Community reviews

Related threats