Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-92594 – Sensitive Information Disclosure (PII via GraphQL) – Craft CMS 5.0.0–5.10.x

Be the first to know when new zero-days emerge:

Summary

CVE-2026-92594 is an unauthenticated information disclosure vulnerability in Craft CMS’s GraphQL API, caused by improper field-level authorization on the draftCreator and revisionCreator fields. It affects Craft CMS 5.0.0-RC1 through versions before 5.11.0 and carries a HIGH severity rating (CVSS v4.0 base score 8.7). When a site’s public GraphQL schema exposes draft or revision data, an attacker with no credentials can harvest personal information belonging to draft and revision creators — typically site editors and administrators.

Technical details

  • Root cause: The draftCreator and revisionCreator GraphQL resolvers are authorized only against the elements.drafts:read and elements.revisions:read scopes, rather than the usergroups.*:read user-data scope normally enforced by Craft’s Gql::canQueryUsers() check.
  • Trigger conditions: The resolvers return a raw User element whose email, username, fullName, and addresses fields carry no per-field authorization. Any client — including an unauthenticated one — holding only the drafts or revisions GraphQL scope can query these fields directly.
  • Attack vector: Network-based, requiring no authentication, no privileges, and no user interaction. Exploitation requires that the site operator has enabled the public GraphQL schema with drafts or revisions scopes.
  • Impact: Disclosure of sensitive personal information (email addresses, usernames, full names, and postal addresses) of draft and revision creators, with no impact on integrity or availability.

Affected software

  • Craft CMS 5.0.0-RC1 up to (but not including) 5.11.0
  • Fixed in Craft CMS 5.11.0

Severity

  • CVSS v3.1 Base Score: 7.5 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
  • CVSS v4.0 Base Score: 8.7 (High) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade Craft CMS to version 5.11.0 or later, which fixes the field-level authorization on draftCreator and revisionCreator.
  • If immediate patching is not possible: Disable or restrict the public GraphQL schema, or remove the elements.drafts:read and elements.revisions:read scopes from any publicly accessible GraphQL token until the upgrade can be applied. Review GraphQL access logs for anomalous queries against draftCreator or revisionCreator fields.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge