Critical WordPress Vulnerability Exploited Immediately After Disclosure
Attackers began exploiting critical WordPress path-traversal CVE-2026-87902 for remote code execution within hours of disclosure.
Patchstack says exploitation of WordPress CVE-2026-87902, a CVSS 9.2 path-traversal flaw in page-template resolution, started within hours of disclosure and reached active compromises by September 23. Unauthenticated attackers can include a chosen local PHP file and, when theme and server preconditions are met, reach remote code execution, including via pearcmd.php when register_argc_argv is enabled. WordPress patched the issue in version 7.1.2 on September 22 and backported the fix through the 4.7.x line. Attack traffic later ran at more than ten times the first evening's volume and progressed from vulnerability checks to PHP writes.
- CVE-2026-87902 is unauthenticated WordPress path traversal scored CVSS 9.2.
- RCE requires specific theme layouts and a readable local PHP file such as pearcmd.php.
- WordPress 7.1.2 fixed it on September 22, with backports through 4.7.x.
- Patchstack saw reconnaissance within hours and active compromises by September 23.
- Later traffic exceeded ten times the first evening, and public scanners exist.
Vulnerabilities mentionedAll →
- CVE-2026-879028.118%Unauthenticated Local File Inclusion to RCE in WordPress Core (fixed in 7.1.2)published · WordPress (WordPress.org) WordPress core KEV PoC ×16
| CVE | Vulnerability | CVSS | EPSS | Flags | Affected | Exposure | Published |
|---|---|---|---|---|---|---|---|
Full article459 words · extracted from securityweek.com · click to collapse
The exploitation of a fresh WordPress vulnerability started within hours of public disclosure and has escalated to active compromises, security firm Patchstack warns.
Tracked as CVE-2026-87902 (CVSS score of 9.2), it is a path traversal flaw in WordPress’ page-template resolution. Under certain conditions, unauthenticated attackers could exploit it for remote code execution.
“An unauthenticated attacker can make get_page_template() page-template resolution include a chosen readable local .php file outside the active theme directories. If relevant pre-conditions for both the server environment and the active theme are met, this can lead to RCE,” WordPress’ advisory reads.
The security defect can be triggered if the name of the top-level directory of the active child or parent theme starts with ‘page-‘ and if the web server account can read a chosen local .php target file that exists on the server.
“The well-known pearcmd.php PEAR→RCE transition can be used for this when register_argc_argv is set to On. The official PHP image for Docker is affected, and the default cPanel configuration is affected when PHP prior to 8.5 is in use,” the advisory reads.
Pearcmd.php provides a command-line tool for the management of PEAR packages in PHP environments and can be abused for RCE on servers with register_argc_argv enabled, especially when combined with a local file inclusion or a path traversal issue.
Advertisement. Scroll to continue reading.
According to WordPress, themes that contain the relevant directory layout include the legacy Twenty Twelve and Twenty Fourteen themes, along with third-party themes such as Neve, Hestia, and Sydney.
The security defect was addressed on September 22 in WordPress version 7.1.2. The fix was also backported to previous WordPress releases, all the way back to 4.7.x.
Within hours of public disclosure, Patchstack identified the first exploitation attempts targeting CVE-2026-87902.
“The payloads match the exact encoding the patch addresses, so whoever built them was working from the diff rather than from an independent discovery,” the security firm notes.
Originating from a small cluster of IP addresses, the initial exploitation activity was designed for reconnaissance, but escalated to active compromises by September 23, Patchstack says.
“Traffic against this CVE is now running at more than ten times the volume we saw on the first evening; it is reaching a far wider spread of sites, and the requests have moved through three clear stages,” the security firm notes.
The attackers first verify whether the target server is vulnerable, then check for PEAR’s pearcmd.php inclusion, and finally abuse pearcmd.php to write PHP content to achieve RCE.
Patchstack suggests that the activity surrounding CVE-2026-87902 is likely to increase, as public scanning tools exist.
Related: WordPress Patches ‘Click2Shell’ Vulnerability
Related: Adobe Patches Critical Flaws in Connect, AEM Forms
Related: Chrome 154 Patches 108 Vulnerabilities
Related: Arista Urges Immediate Patching of Exploited VCO Zero-Day