CVE-2026-123707 json
WPGraphQL < 2.27.1 - Contributor+ Custom Post Status Content Disclosure
published 4h ago modified 3h ago also EUVD-2026-125985
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Unknown WPGraphQL 2.27.1
Is CVE-2026-123707 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploits and checks
- wpscan.com https://wpscan.com/vulnerability/ae3506eb-c023-4af6-b3c0-5c2600b2b502/ referenced PoC, tagged "exploit" by a source, unverified
Affected products
- Unknown WPGraphQL
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Technology feeds
References
-
wpscan.com
/vulnerability/ae3506eb-c023-4af6-b3c0-5c2600b2b502/
exploit, vdb-entry, technical-description
Sources
- CVE List CVE-2026-123707
- NVD CVE-2026-123707
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.