WordPress Core 4.7.0 — 7.1.2 - Unauthenticated Sensitive Information Exposure via Comment Feeds
CVE-2026-66666Published · Updated Action summary
Affected: ≤7.1.2Update to 4.7.38 or 4.8.33 or 4.9.34 or 5.0.30 or 5.1.27 or 5.2.29 or 5.3.26 or 5.4.24 or 5.5.23 or 5.6.22 or 5.7.20 or 5.8.18 or 5.9.19 or 6.0.17 or 6.1.15 or 6.2.14 or 6.3.13 or 6.4.13 or 6.5.13 or 6.6.10 or 6.7.10 or 6.8.11 or 6.9.10 or 7.0.7 or 7.1.3 or newer
Fixed versions are per release branch: update to the fix for the branch you run.
All remediation steps- Severity
- Medium5.3
- CVSS
- 5.3CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NWhat does this vector mean?
AV:NAttack vector- Network
AC:LAttack complexity- Low
PR:NPrivileges required- None
UI:NUser interaction- None
S:UScope- Unchanged
C:LConfidentiality- Low
I:NIntegrity- None
A:NAvailability- None
- Required access
- No account needed
- Exploit prediction (EPSS)
- 0.4% chance in 30 days35th percentile
- CISA KEV
- Not listed
On this page7
Am I affected?
WordPress wordpress
- Affected≤ 7.1.2
- Patched in4.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
Update to 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 or newer.
You are affected if you run ≤ 7.1.2. 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 and later are not affected by this issue.
- Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under WordPress.
- No admin access? Run a passive check of your site. It reads public files only.
- No account is needed to exploit this. Treat any exposed site on an affected version as at risk.
What to do
- 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
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
- Watch WordPress to get an email when the next vulnerability is published.
Advisory
Source description from Wordfence Intelligence, credited to Ananda Dhakal.
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.
Exploits & references
Proof-of-concept & detection
No public proof-of-concept or detection template is known for this vulnerability.
Advisories & patches
- Advisorywordfence.com
Timeline
CVE published
Severity medium, CVSS 5.3
Record last updated
Sources & licenses
Wordfence record- Vulnerability data
- Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
- CVE® identifiers
- Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
- CVSS / CWE
- National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
- EPSS
- Exploit Prediction Scoring System by FIRST.org.
- VulnCrest content
- Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.