Craft CMS 5.0.0 before 5.11.2 GraphQL Schema Scope Bypass via prev/next
Affects Craft CMS 5.0.0 before 5.11.2 where GraphQL is enabled and the schema grants read on some sections but withholds others that share an entry type. Fixed in 5.11.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 5.11.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 5.11.2.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Craft CMS versions from 5.0.0 before 5.11.2 contain an authorization bypass in their GraphQL API. Remote, anonymous attackers can use the prev/next fields to walk from one visible entry to others, reading titles, slugs, and custom-field content from sections that should be withheld.
Read the original description
Craft CMS from 5.0.0 before 5.11.2 contains an authorization bypass vulnerability that allows anonymous GraphQL clients to read out-of-scope section entries via prev/next fields. Attackers can chain next hops from one visible in-scope entry to enumerate entries and read titles, slugs, and custom-field content from withheld sections.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.3/10CVSS 9.3
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 5.11.2.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- craftcms cms
From 5.0.0 · fixed in 5.11.2
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124427
Is CVE-2026-124427 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A GraphQL query can read entries in sections the site operator deliberately excluded from the schema. The exposed data includes titles, slugs, UIDs, post dates, and full custom-field content, and chaining next hops lets a caller enumerate the site's entry list.Source: github.com
Which versions are affected by CVE-2026-124427?
cms: from 5.0.0 before 5.11.2.Source: cve.now feed data
Am I affected, and how do I check?
Craft CMS versions from 5.0.0 up to but not including 5.11.2. The issue needs GraphQL enabled with a public schema or a scoped private token, and a schema that grants read on one section while withholding another section that shares an entry type. Check the installed version in composer.lock or the control panel, and review the GraphQL schema settings for those section permissions.Source: github.com
How do I fix CVE-2026-124427?
Upgrade Craft CMS to 5.11.2 or later, which contains the fix.Source: github.com