CVE-2026-123707 in WPGraphQL Plugininfo

Summary

by MITRE • 11/15/2026

The WPGraphQL WordPress plugin before 2.27.1 does not restrict access to posts in custom non-public post statuses, allowing users with the Contributor role and above to read the content of other users' posts in those statuses.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Analysis

by VulDB Data Team • 11/15/2026

The vulnerability identified in versions of the WPGraphQL plugin prior to release 2.27.1 represents a significant authorization flaw within WordPress-based environments that utilize GraphQL for data retrieval. This issue specifically targets custom post types configured with non-public post statuses, such as draft, pending, or private states which are typically intended to be inaccessible to standard users and even often hidden from public listings in the administrative interface. The core technical failure lies in the plugin's query resolution logic, where it fails to enforce proper capability checks when resolving fields related to these specific post types. Consequently, any authenticated user possessing a Contributor role or higher gains the ability to execute GraphQL queries that bypass standard WordPress permission filters. This allows them to retrieve the full content of posts belonging to other users who are in non-public status states, effectively circumventing the intended isolation between different author accounts and security tiers within the application.

From an operational perspective, this vulnerability facilitates unauthorized data access and potential information disclosure. An attacker with a low-privileged account can enumerate and extract sensitive content that was never meant for their consumption. This includes unpublished articles, draft proposals, or private communications stored as posts. The impact extends beyond simple privacy violations; it undermines the integrity of collaborative workflows where multiple users contribute to a single site. For organizations relying on WordPress for internal documentation or restricted publishing, this flaw exposes confidential intellectual property and personal data. Furthermore, because GraphQL allows complex nested queries, an attacker could potentially automate the extraction of large volumes of such restricted content with minimal effort, leading to significant reputational damage and potential regulatory non-compliance depending on the nature of the exposed data.

This vulnerability aligns closely with CWE-284 Improper Access Control, as it involves a failure to restrict access to resources based on user privileges or object state. It also maps to MITRE ATT&CK technique T1078 Valid Accounts, where an adversary uses legitimate credentials to gain unauthorized access to specific data objects that should be restricted by their status rather than just their role level. The flaw highlights the complexity of securing GraphQL endpoints in CMS platforms, as they often expose more granular data structures than traditional REST APIs, requiring rigorous validation at every layer of query resolution.

To mitigate this risk, administrators must immediately upgrade the WPGraphQL plugin to version 2.27.1 or later, where these access restrictions have been corrected to properly respect post status permissions for all user roles. In environments where immediate patching is not feasible due to dependency constraints, temporary mitigation strategies should be implemented at the web application firewall level to block GraphQL endpoints if they are not actively required by frontend applications. Additionally, security audits of custom plugins and themes interacting with WPGraphQL should be conducted to ensure no other code paths bypass these newly enforced restrictions. Regular monitoring for unusual query patterns targeting non-public post statuses can also aid in detecting exploitation attempts before significant data loss occurs.

Responsible

WPScan

Reservation

11/06/2026

Disclosure

11/15/2026

Moderation

accepted

CPE

ready

EPSS

0.00140

KEV

no

Activities

very low

Sources

Might our Artificial Intelligence support you?

Check our Alexa App!