CVE-2026-71427
Received Received - Intake

WPGraphQL Content Blocks Password-Protected Post Exposure

Vulnerability report for CVE-2026-71427, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-18

Last updated on: 2026-11-18

Assigner: GitHub, Inc.

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-18
Last Modified
2026-11-18
Generated
2026-11-19
AI Q&A
2026-11-19
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
wpgraphql content_blocks to 4.8.6 (exc)
wpengine wp-graphql-content-blocks to 4.8.6 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
CWE-200 The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects the WPGraphQL Content Blocks WordPress plugin before version 4.8.6. It allows unauthenticated attackers to retrieve the full content of password-protected posts by exploiting the editorBlocks renderedHtml field in GraphQL queries. The flaw bypasses normal content access controls by directly resolving post content without checking if the post is password-protected.

Detection Guidance

Check if your WordPress site uses wp-graphql-content-blocks plugin version below 4.8.6. Use GraphQL queries to test if password-protected post content is exposed via the editorBlocks.renderedHtml field. Example: curl -X POST -H 'Content-Type: application/json' -d '{"query":"{post(id:POST_ID){editorBlocks{renderedHtml}}}"}' YOUR_GRAPHQL_ENDPOINT

Impact Analysis

If you use this plugin with WordPress, an attacker could access sensitive content like paid articles, member-only content, previews, or internal documents without authentication. This exposes private information even when posts are set to password-protected, potentially leading to data breaches or unauthorized access to restricted material.

Compliance Impact

This vulnerability could lead to non-compliance with GDPR, HIPAA, or other privacy regulations by exposing sensitive personal or health data. Unauthorized access to password-protected content may violate data protection requirements for confidentiality and access controls, potentially resulting in legal penalties or reputational damage.

Mitigation Strategies

Update the wp-graphql-content-blocks plugin to version 4.8.6 or later immediately. If updating is not possible, disable the plugin temporarily until the update is applied. Review GraphQL API access logs for suspicious queries targeting the editorBlocks field.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-71427. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...