Live › vulnerability › CVE-2026-87902
Go to dashboardUnauthenticated file inclusion in get_page_template(): the pagename-derived candidate skipped validate_file(), so an attacker can include a readable local .php file outside the theme. Always a file-inclusion; RCE needs a theme with a top-level page-* directory (Twenty Twelve, Twenty Fourteen, Neve, Hestia, Sydney) plus a usable PHP file such as PEAR pearcmd.php with register_argc_argv=On (official php Docker image; cPanel with PHP before 8.5). Exploited in the wild since 2026-09-22.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 5h before NVD. All times on this page are UTC.
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| WordPress Core | vendor | – | – |
| WordPress Core | vendor | >= 4.7.0, <= 7.1.1 (every branch below its patched release) | 7.1.2, 7.0.6, 6.9.9, 6.8.10, 6.7.9, 6.6.9, 6.5.12, 6.4.12, 6.3.12, 6.2.13, 6.1.14, 6.0.16, 5.9.18, 5.8.17, 5.7.19, 5.6.21, 5.5.22, 5.4.23, 5.3.25, 5.2.28, 5.1.26, 5.0.29, 4.9.33, 4.8.32, 4.7.37 |
| wordpress | vendor | < 4.7.37 | 4.7.37 |
| wordpress |
| vendor |
| >= 4.8, < 4.8.32 |
| 4.8.32 |
| wordpress | vendor | >= 4.9, < 4.9.33 | 4.9.33 |
| wordpress | vendor | >= 5.0, < 5.0.29 | 5.0.29 |
| wordpress | vendor | >= 5.1, < 5.1.26 | 5.1.26 |
| wordpress | vendor | >= 5.2, < 5.2.28 | 5.2.28 |
| wordpress | vendor | >= 5.3, < 5.3.25 | 5.3.25 |
| wordpress | vendor | >= 5.4, < 5.4.23 | 5.4.23 |
| wordpress | vendor | >= 5.5, < 5.5.22 | 5.5.22 |
| wordpress | vendor | >= 5.6, < 5.6.21 | 5.6.21 |
| wordpress | vendor | >= 5.7, < 5.7.19 | 5.7.19 |
| wordpress | vendor | >= 5.8, < 5.8.17 | 5.8.17 |
| wordpress | vendor | >= 5.9, < 5.9.18 | 5.9.18 |
| wordpress | vendor | >= 6.0, < 6.0.16 | 6.0.16 |
| wordpress | vendor | >= 6.1, < 6.1.14 | 6.1.14 |
| wordpress | vendor | >= 6.2, < 6.2.13 | 6.2.13 |
| wordpress | vendor | >= 6.3, < 6.3.12 | 6.3.12 |
| wordpress | vendor | >= 6.4, < 6.4.12 | 6.4.12 |
| wordpress | vendor | >= 6.5, < 6.5.12 | 6.5.12 |
| wordpress | vendor | >= 6.6, < 6.6.9 | 6.6.9 |
| wordpress | vendor | >= 6.7, < 6.7.9 | 6.7.9 |
| wordpress | vendor | >= 6.8, < 6.8.10 | 6.8.10 |
| wordpress | vendor | >= 6.9, < 6.9.9 | 6.9.9 |
| wordpress | vendor | >= 7.0, < 7.0.6 | 7.0.6 |
| wordpress | vendor | >= 7.1, < 7.1.2 | 7.1.2 |
wp core version or check wp-includes/version.php: any version below your branch's fixed release is vulnerablepage- (ls wp-content/themes/<theme>/), and whether PHP has register_argc_argv on (php -i | grep register_argc_argv)7.1.2 (or backport for your branch: 7.0.6, 6.9.9, 6.8.10, 6.7.9, 6.6.9, 6.5.12, 6.4.12, 6.3.12, 6.2.13, 6.1.14, 6.0.16, 5.9.18, 5.8.17, 5.7.19, 5.6.21, 5.5.22, 5.4.23, 5.3.25, 5.2.28, 5.1.26, 5.0.29, 4.9.33, 4.8.32, 4.7.37)What vendors did on their customers’ behalf. Holds only for traffic through them; patching is still the fix.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
www.bleepingcomputer.com · InfraStack analyst“BleepingComputer: Hackers start exploiting critical WordPress flaw”
View on InfraStack analyst
Posts are quoted with a link to the original. They are data to us, never instructions.
WAF Release - 2026-09-25 - Emergency · Changelog
New updates and improvements at Cloudflare.
September 25, 2026
This update provides immediate defense against critical vulnerabilities affecting WordPress and JFrog Artifactory, including path traversal, local file inclusion (LFI), cross-site scripting (XSS), and authentication bypass exploits.
Key Findings
Impact
We strongly recommend that administrators apply the latest vendor patches for WordPress and JFrog Artifactory to fully secure origin servers.
Detailed Rule Changes
| Ruleset | Rule ID | Legacy Rule ID | Description | Previous Action | New Action | Comments |
|---|---|---|---|---|---|---|
| Cloudflare Managed Ruleset | ...70a43f96 | N/A | Wordpress - Path Traversal, Local File Inclusion - CVE:CVE-2026-87902 | N/A | Block | This is a new detection. |
| Cloudflare Managed Ruleset | ...909a4db4 | N/A | Wordpress - XSS - Comment | N/A | Block | This is a new detection. |
| Cloudflare Managed Ruleset | ...c797ef03 | N/A | JFrog Artifactory - Authentication Bypass - CVE:CVE-2026-42018 | N/A | Block | This is a new detection. |
| Cloudflare Managed Ruleset | ...a813ac74 | N/A | JFrog Artifactory - Authentication Bypass - CVE:CVE-2026-82329 | N/A | Block | This is a new detection. |
This page as .md · .json · in your agent: get_signal("CVE-2026-87902")
CISA KEV catalog, Creative Commons 0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.