WPGraphQL Content Blocks is a WordPress plugin that extends WPGraphQL to support querying Gutenberg blocks as data. Prior to 4.8.6, the editorBlocks renderedHtml field in includes/Data/ContentBlocksResolver.php uses resolve_content_blocks() to read a post with get_post() without applying post_password_required(). An unauthenticated caller who knows a supported post identifier can therefore retrieve the complete body of a password-protected published post without a post password, nonce, or valid cookie, exposing paid, member-only, preview, or internal content. This issue is fixed in version 4.8.6.
Severity
CVSS 3.1
5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 28th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-18. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-200Exposure of Sensitive Information to an Unauthorized Actor CWE-862Missing Authorization
Show the promptExplain CVE-2026-71427 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-71427?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-71427?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-71427 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.