EUVD-2026-104582
GHSA-vgpq-xf77-c94c
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain site-A-scoped GraphQL token
-
DeliveryCraft mutation with foreign siteId
-
ExploitBypass unenforced requireAllowedSite()
-
ExecutionCreate/delete content in site B
-
ImpactCorrupt or destroy cross-site data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires a multi-site Craft CMS installation (5.0.0 up to but not including 5.11.0) with the GraphQL API enabled and at least one site-scoped GraphQL token in the attacker's possession that permits mutations. The attacker supplies a siteId for a site outside the token's scope; because requireAllowedSite() is not enforced on mutation resolvers, cross-site create/delete operations succeed. Limiting factors: the attacker must hold a valid (even if narrowly scoped) GraphQL mutation token, the install must be multi-site with content shared across sites, and GraphQL mutations must be enabled - single-site installs and read-only GraphQL schemas are not affected. |
| Impact | This is a genuinely high-priority authorization bypass (CWE-863) in Craft CMS multi-site installations. The input CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H, 9.3) rates it network-exploitable with no privileges, but this conflicts with the description: exploitation requires the attacker to already hold a valid site-scoped GraphQL token (site A). That is a credential, so the PR:N in the published vector overstates openness - a token is a prerequisite, and I assess PR:L rather than PR:N. There is no EPSS score, no CISA KEV listing, and no public exploit referenced in the supplied data, so this is not confirmed as actively exploited - the priority rests on severity and ease of abuse (low complexity, no user interaction) rather than observed in-the-wild activity. The published vector also sets VC:H (high confidentiality impact), which appears overstated: the flaw enables cross-site mutations (creating and deleting content), not unauthorized reads, so the real impact is to integrity and availability. Net: a real, actionable fix-now issue for multi-site Craft operators who issue scoped GraphQL tokens, but not a mass-exploitation internet-wide crisis given the token prerequisite and absence of exploitation signals. |
| Exploit ScenarioDerived | An attacker (or a compromised/semi-trusted integration) holds a GraphQL token scoped to site A on a multi-site Craft CMS install. Because requireAllowedSite() is not enforced on mutations, they issue GraphQL mutations specifying a siteId for site B, creating rogue entries in site B and deleting entries, categories, tags, and assets shared across sites. No public exploit code is identified at time of analysis, but the attack requires only low-complexity crafted GraphQL requests over the network with no user interaction. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 19, 2026
Authorization bypass in Craft CMS 5.0.0 through 5.10.x allows an authenticated holder of a narrowly site-scoped GraphQL token to create entries in other sites and to delete entries, categories, tags and assets shared across sites. The bypass exists because the requireAllowedSite() check applied to GraphQL queries is not enforced on mutation resolvers, so an attacker can simply supply a siteId outside the token's scope and have the write succeed. Only multi-site installations with the GraphQL API and mutation-enabled, site-scoped tokens are exposed; single-site installs and read-only GraphQL schemas are not affected, and no public exploit code or confirmed active exploitation was identified at time of analysis. Impact is integrity and availability only (no confidentiality loss), but deletion of shared elements can corrupt content consumed by multiple sites.
RemediationAI
Vendor-released patch: upgrade Craft CMS to 5.11.0 or later, which enforces requireAllowedSite() on mutation resolvers; the fix is documented in GHSA-7rr3-4jcm-x526 (https://github.com/craftcms/cms/security/advisories/GHSA-7rr3-4jcm-x526) with additional detail at https://www.vulncheck.com/advisories/craft-cms-5.0.0-before-5.11.0-graphql-site-scope-bypass-via-mutations. If upgrading cannot be done immediately, revoke or rotate every site-scoped GraphQL token and reissue only tokens whose holders are fully trusted, since any valid mutation-capable token is sufficient for exploitation; the trade-off is disruption to integrations and headless front-ends that depend on those tokens. Alternatively, disable GraphQL mutations (or the GraphQL API entirely) in settings until patched, accepting that any headless or mobile client relying on GraphQL writes will break, and audit recent content changes for entries created in unexpected sites or for deletions of shared categories, tags and assets. Restricting cross-site sharing of elements reduces blast radius but does not close the bypass and requires content-model changes.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Craft CMS exposes a GraphQL API whose schema can be partitioned by token scope, including per-site restrictions. The intended control is a requireAllowedSite() helper that validates a requested siteId against the sites permitted to the calling token; in versions 5.0.0 through 5.10.x this check is wired into query handling but omitted from mutation resolvers, a classic incorrect-authorization weakness (CWE-863). As a result, a token issued for site A can pass siteId=B to save mutations and write entries into site B, and can invoke delete mutations against elements (entries, categories, tags, assets) that are shared across sites, affecting content rendered on every site that references them. The vulnerability is reachable over the network with no user interaction and no special configuration beyond a multi-site install with GraphQL mutations enabled; the independent assessment scores it CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H, reflecting that a valid token is required (authenticated), that only integrity and availability of cross-site content are impacted, and that no scope change occurs. The broader CPE entry for the craftcms:cms package is wildcarded, so version determination must come from the vendor advisory rather than CPE matching.
Know when Cms gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
A valid site-scoped GraphQL mutation token is required, so PR:L not PR:N; the flaw enables create/delete (integrity and availability high) but not data reads, so C:N.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
Craft CMS from 5.0.0 before 5.11.0 contains an authorization bypass vulnerability that allows site-scoped GraphQL tokens to mutate other sites' content because requireAllowedSite() is not enforced. Attackers holding a site-A token can create entries in site B via supplied siteId and delete entries, categories, tags, and assets shared across sites.
Technical POC Analysis
CWE-863 Incorrect Authorization.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
Craft CMS versions 5.0.0 through 5.10.x contain a critical authorization bypass that lets a site-scoped GraphQL token perform writes and deletions beyond its intended site, affecting multi-site installations that expose mutation-enabled GraphQL tokens. Leadership should care because misuse can alter or delete shared content consumed by multiple sites, creating integrity and availability risk for content operations and customer-facing sites. Exposure is limited to multi-site GraphQL mutation deployments, and no public exploit identified at time of analysis.
Disable GraphQL mutation resolvers for site-scoped tokens; use read-only GraphQL schemas; revoke or rotate mutation-enabled site-scoped tokens; restrict GraphQL endpoint access to trusted networks; monitor for out-of-scope siteId writes and deletions; maintain and test backups of shared multi-site content. No vendor-released patch identified at time of analysis.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Cayin CMS suffers from an authenticated OS semi-blind command injection vulnerability using default credentials. Rated c
Multiple integer underflows in the icmLut_allocate function in International Color Consortium (ICC) Format library (iccl
phpKF CMS 3.00 Beta allows unauthenticated PHP file upload by disguising it as a PNG, then renaming it for execution. Po
Deserialization of Untrusted Data in the Sitecore.Security.AntiCSRF (aka anti CSRF) module in Sitecore CMS 7.0 to 7.2 an
Deserialization of Untrusted Data in the anti CSRF module in Sitecore through 9.1 allows an authenticated attacker to ex
Unauthenticated file disclosure in LavaLite CMS through 10.1.2 allows remote attackers to download private stored files
Authenticated remote code execution in Craft CMS versions 5.5.0 through 5.9.13 allows admin users to execute arbitrary P
SQL injection vulnerability in hava_post.php in Havalite CMS 1.1.0 and earlier allows remote attackers to execute arbitr
Unrestricted file upload vulnerability in hava_upload.php in Havalite CMS 1.1.0 and earlier allows remote attackers to e
Cross-site request forgery (CSRF) vulnerability in Ilch CMS allows remote attackers to hijack the authentication of admi
Multiple cross-site scripting (XSS) vulnerabilities in Havalite 1.0.4 and earlier allow remote attackers to inject arbit
A security vulnerability in juzaweb CMS (CVSS 6.3). Risk factors: public PoC available.
Exploit-DB