Craft CMS 5.0.0 up to (but not including) 5.11.0 has an authorization bypass: a GraphQL token scoped to one site can create and delete content on other sites in the same install.
What Is It
CVE-2026-112776 is an authorization bypass in Craft CMS, classified as CWE-863 (Incorrect Authorization). Affected versions don't run the requireAllowedSite() check on GraphQL mutations. Because of that, a site-scoped token isn't limited to the site it was issued for.
An attacker holding a token for site A can:
- Create entries in site B by setting the
siteIdvalue - Delete entries, categories, tags and assets that are shared across sites
VulnCheck reported the issue on 2026-10-19. NVD lists it as "Deferred."
Why It Matters
VulnCheck scores it 9.8 CRITICAL under CVSS 3.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and 9.3 CRITICAL under CVSS 4.0. Both vectors describe a network attack with low complexity, no privileges required and no user interaction. Confidentiality, integrity and availability impacts are all rated high.
Note that the description says the attacker must hold a valid site-scoped GraphQL token. That doesn't quite match the "no privileges required" rating, but the score is reported here as published.
This mainly affects multi-site Craft installs where GraphQL tokens are split by site, for example separate brands, regions or tenants. In those setups, a leaked or low-trust token for one site could be used to change or delete content on another.
KEV status: No CISA KEV entry was provided for this CVE. Active exploitation is not confirmed by KEV at this time.
What's Vulnerable
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| craftcms | cms | 5.0.0 to before 5.11.0 | 5.11.0 |
The vendor data marks all other versions as unaffected. NVD lists no CPEs for this record.
Patch Status
Version 5.11.0 is listed as unaffected and is the fixed release. Teams running Craft CMS 5.x below 5.11.0 should upgrade to 5.11.0 or later.
No CISA KEV required action or due date applies, since there is no KEV listing. Until patched, consider which GraphQL tokens are active in multi-site deployments and who holds them. The vendor's GitHub advisory and VulnCheck's advisory are linked below.