CVE
WPGraphQL Content Blocks unauthenticated disclosure in editorBlocks.renderedHtml
- Exploited
- No known exploitation
- Fix
- Fixed in 4.8.6
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.8.6.
Summary
Unauthenticated attackers can use the WPGraphQL Content Blocks plugin from wpengine to read the full body of password-protected published posts over the network, without logging in. An attacker only needs to know a supported post identifier to get the content, which can include paid, member-only, preview, or internal material.
Original 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.
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 30 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 4.8.6.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-71427 (WPGraphQL Content Blocks: Unauthenticated Sensitive Information Disclosure via editorBlocks.renderedHtml), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-71427 (entry last updated 2026-11-18):
Affected:
- wpengine wp-graphql-content-blocks: fixed in 4.8.6
Fixed versions: 4.8.6.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-71427 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-71427 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/wpengine/wp-graphql-content-blocks/security/advisories/GHSA-mj4c-3882-m65q
- https://github.com/wpengine/wp-graphql-content-blocks/commit/693ea8ab59f15f84748bae264a81219946c731bc
- https://github.com/wpengine/wp-graphql-content-blocks/releases/tag/v4.8.6
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-71427
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-71427"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- wpengine wp-graphql-content-blocks
fixed in 4.8.6
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · wpengine/wp-graphql-content-blocks · Advisory GHSA-mj4c-3882-m65q |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-71427 |
| Record | NVD · CVE-2026-71427 |
| Other links 2 | |
| Repository | GitHub · wpengine/wp-graphql-content-blocks · Commit 693ea8ab |
| Repository | GitHub · wpengine/wp-graphql-content-blocks · Release v4.8.6 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-71427
Is CVE-2026-71427 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-71427?
wp-graphql-content-blocks: before 4.8.6.Source: cve.now feed data
How do I fix CVE-2026-71427?
Upgrade to a fixed version: 4.8.6.Source: cve.now feed data