WordPress Core <= 7.0.2 - Unauthenticated Sensitive Information Exposure via Comment Feeds

2026-08-08 00:00
Elio Gubser (odkdn1)

Strategic Overview

Status
Patched in 4.7.34
Affected Core
WordPress 7.0
Affected Version
4.7.0 – 7.0.2 · 24 branches
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE pending
View all WordPress 7.0 vulnerabilities

At a glance

This record tracks a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WordPress 7.0 WordPress release line, affecting 4.7.0 – 7.0.2 · 24 branches. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.7.34; sites on affected versions should update now. Disclosed August 2026, reported by Elio Gubser (odkdn1).

Vulnerability Overview

WordPress Core is vulnerable to Sensitive Information Exposure in all versions up to, and including, 7.0.2 via the comment feeds due to insufficient restrictions on internal notes, which are not excluded from feed output. This makes it possible for unauthenticated attackers to extract the contents of internal notes that should only be available to privileged users.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in WordPress 7.0 4.7.0 – 7.0.2 · 24 branches takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For WordPress 7.0 the fix is 4.7.34: builds 4.7.0 – 7.0.2 · 24 branches are affected, anything from 4.7.34 onward is not.

Remediation

Update to one of the following versions, or a newer patched version: 4.7.34, 4.8.29, 4.9.30, 5.0.26, 5.1.23, 5.2.25, 5.3.22, 5.4.20, 5.5.19, 5.6.18, 5.7.16, 5.8.14, 5.9.14, 6.0.13, 6.1.11, 6.2.10, 6.3.9, 6.4.9, 6.5.9, 6.6.6, 6.7.6, 6.8.7, 6.9.6, 7.0.3

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: updating to 4.7.34 is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/c3f9898b-0aa0-4dd1-9298-96c853dbef5c

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C