On this page (7 sections)

A critical flaw tracked as CVE-2026-124427 affects Craft CMS from 5.0.0 before 5.11.2. According to the GitHub Advisory Database entry, anonymous GraphQL clients can read section entries that are outside their allowed scope by using the prev and next fields.

If you run a Craft CMS 5 site with the GraphQL API enabled, especially one that keeps drafts, members-only content or unpublished material in sections that the public schema is not supposed to expose, this is worth checking today.

What happened

The advisory was published on November 8, 2026 and describes an authorization bypass in Craft CMS's GraphQL handling. The NVD record carries the same description. It is a copy of the original text, not separate confirmation, and at the time of writing only one independent publisher covers the story.

A VulnCheck advisory is also referenced, along with a Craft CMS GitHub security advisory. The research available for this article contained only the short description from these records, so details beyond it, such as the exact code change, are not covered here.

How the weakness works

Craft CMS lets site owners define GraphQL schemas that control which sections an API client may query. An anonymous visitor typically gets a public schema that exposes only some sections, for example published blog posts, while others stay out of scope.

The reported problem is that the prev and next fields, which navigate from one entry to its neighbor, did not enforce those section limits. Per the advisory, an attacker can start from one entry they are allowed to see and chain next hops to enumerate entries in sections that were meant to be withheld. Titles, slugs and custom-field content from those entries can be read.

This is a classic missing-authorization problem (CWE-862). The main query path checks permissions, but a secondary path that reaches the same data does not. No login is needed, and the CVSS vector in the advisory lists network access, low complexity, no privileges and no user interaction.

The advisory describes data exposure of entries in out-of-scope sections. The CVSS metrics also rate integrity and availability impact as high on the vulnerable system, but the description itself only mentions reading content. We are not aware of details supporting more than that.

Who is realistically exposed

  • Sites on Craft CMS 5.0.0 up to, but not including, 5.11.2.
  • Sites where the GraphQL API is reachable by anonymous clients (a public schema is configured).
  • Sites that hold content in sections excluded from that public schema, such as drafts, internal notes, partner-only pages or content scheduled for later release.
  • Headless setups where a front end calls Craft over GraphQL, since the endpoint is usually public by design.

If your public schema already exposes every section, or GraphQL is not used, the practical impact of this specific flaw is smaller, but you should still update. Sites on Craft 4 are outside the affected range stated in the advisory.

How to check your exposure

First confirm your installed version. This read-only Composer command, run from your project root, prints the installed Craft CMS package version. Anything from 5.0.0 up to before 5.11.2 is in the affected range.

Show the installed Craft CMS version (run in the project root)Shell
composer show craftcms/cms

You can also read the version in the Craft control panel utilities or system report. Next, review your GraphQL setup in the control panel under GraphQL, and note which sections each schema, especially the public one, can query.

Finally, search your web server or application logs for unusual GraphQL traffic. Look for a single client sending many repeated requests to your GraphQL endpoint in a short time, particularly queries that request next or prev fields. The exact endpoint path depends on your configuration, so adjust the pattern below.

Count GraphQL requests per client IP in an access log (adjust the log path and endpoint)Shell
grep -i "graphql" /var/log/nginx/access.log | awk '{print $1}' | sort | uniq -c | sort -rn | head

A high count from one address is not proof of abuse, since headless front ends also call the API often. Most front-end calls come from your own servers or known build systems, so unfamiliar addresses stand out. Request bodies are usually not in standard access logs, so you may not be able to tell which fields were queried.

What to do now

  1. Identify every Craft CMS 5 site you run, including staging and forgotten projects, and record the installed version.
  2. Update to Craft CMS 5.11.2 or later, following the project's normal update process and testing on staging first.
  3. Back up the database and files before updating.
  4. Review which sections are exposed in each GraphQL schema and remove any that do not need to be public.
  5. If you do not use GraphQL at all, disable public access to the endpoint until you have patched.
  6. Check logs for repeated anonymous GraphQL requests from unfamiliar addresses.
  7. Assume content in withheld sections may have been read if you see suspicious traffic, and decide whether anything sensitive needs to be rotated or disclosed.

To update through Composer, run the following from your project root. It pulls the newest release allowed by your composer.json constraints. If your constraint pins an older version, edit it first.

Caution. Updating a CMS can change behavior and run database migrations. Take a full backup and test on a staging copy before updating production.
Update Craft CMS via Composer (run in the project root, then confirm the version)Shell
composer update craftcms/cms
composer show craftcms/cms

After the update, run any pending migrations through your usual Craft process and confirm the reported version is 5.11.2 or higher.

Detection and monitoring afterwards

Because this flaw exposes data without leaving obvious errors, ongoing visibility matters more than a one-time check. Consider logging GraphQL request bodies on a protected channel, or rate limiting the endpoint at your reverse proxy or firewall, so that chained enumeration stands out and slows down. A website firewall can help add that kind of rate control, but it is not a substitute for patching.

Keep a short inventory of CMS versions across your sites and check it whenever new advisories appear. A read-only security scan of sites you have verified can help you spot outdated or exposed components from the outside, and change monitoring can alert you to unexpected changes. Neither can tell you whether data was read through this flaw.

What we do not know yet

  • Whether the flaw is being exploited. The research shows no CISA KEV entry and no reports of attacks, which is not proof that none exist.
  • The exact patched version list. The GitHub entry shows patched versions as unknown, so the fix in 5.11.2 is inferred from the affected range stated in the description.
  • Technical specifics of the fix, since the available sources contain only the short description.
  • Whether other Craft CMS branches are affected. The advisory only names 5.0.0 before 5.11.2.

Check the official Craft CMS security advisory linked above for the authoritative fixed-version information and any workarounds.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-124427 - GitHub Advisory Databasegithub.com
  2. CVE-2026-124427: 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…nvd.nist.gov ·
  • Craft CMS
  • GraphQL
  • CVE-2026-124427
  • authorization bypass
  • CMS security