CVE-2026-66666

WordPress Core 4.7.0 - 7.1.2 - Unauthenticated Sensitive Information Exposure via Comment Feeds

2026-10-07 00:00
Ananda Dhakal

Strategic Overview

Status
Patched in 4.7.38
Affected Core
WordPress 7.1
Affected Version
4.7.0 – 7.1.2 · 25 branches
CVSS
5.3Medium
Weakness type
CWE-201 · Insertion of Sensitive Information Into Sent Data
CVE
CVE-2026-66666
View all WordPress 7.1 vulnerabilities

At a glance

CVE-2026-66666 is a medium-severity Insertion of Sensitive Information Into Sent Data vulnerability in the WordPress 7.1 WordPress release line, affecting 4.7.0 – 7.1.2 · 25 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.38; sites on affected versions should update now. Disclosed October 2026, reported by Ananda Dhakal.

Vulnerability Overview

WordPress Core is vulnerable to sensitive information exposure in versions 4.7 through 7.1.2 because singular comment feeds load approved comments before verifying that the associated post is viewable. This makes it possible for unauthenticated attackers to retrieve comments associated with private, draft, or otherwise unpublished posts when the relevant post identifier or slug is known or discovered.

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-201: Insertion of Sensitive Information Into Sent Data

The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.

Remediation

Update to one of the following versions, or a newer patched version: 4.7.38, 4.8.33, 4.9.34, 5.0.30, 5.1.27, 5.2.29, 5.3.26, 5.4.24, 5.5.23, 5.6.22, 5.7.20, 5.8.18, 5.9.19, 6.0.17, 6.1.15, 6.2.14, 6.3.13, 6.4.13, 6.5.13, 6.6.10, 6.7.10, 6.8.11, 6.9.10, 7.0.7, 7.1.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.38 is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-66666https://www.wordfence.com/threat-intel/vulnerabilities/id/7cef819e-71a3-4fe0-9d32-8d0e292bb904https://nvd.nist.gov/vuln/detail/CVE-2026-66666

Related records

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