CVE-2026-123707: WPGraphQL (WordPress plugin) · Information Exposure
Affects WPGraphQL (WordPress plugin)Source CVE Database V5
Not known to be exploited : upgrade to 2.27.1 when convenient.
Data as of 15 Nov 2026, 06:23 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 2.27.1
Exploitation evidence
Disclosed: evidence found.
CVE published 15 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.
What to do
Upgrade WPGraphQL (WordPress plugin) to 2.27.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WPGraphQL | Affected
| Fixed in
|
AI-suggested
Upgrade WPGraphQL to version 2.27.1 or later, where this access control issue has been fixed. No other mitigation is required once the plugin is updated.
Description
A vulnerability in the WPGraphQL WordPress plugin before version 2.27.1 allows users with the Contributor role and above to access posts in custom non-public post statuses that they should not be able to read. This exposure of sensitive information occurs because the plugin does not properly restrict access to these posts.