WordPress core remote file inclusion under active exploit (CVE-2026-87902)
A remote file inclusion vulnerability in WordPress core (CVE-2026-87902) can be escalated to unauthenticated remote code execution. It is actively exploited in the wild and was added to CISA’s Known Exploited Vulnerabilities catalog on September 25, 2026.
Update, October 8, 2026
Exploitation has escalated since disclosure. Patchstack telemetry recorded
probing within five hours of the 7.1.2 release and full exploitation within
about a day, with traffic rising roughly tenfold as attackers moved from
scanning to payload delivery. Attackers are now including pearcmd.php to
write PHP files to disk, and public scanning tooling for this CVE is in
circulation. CISA’s September 28 remediation deadline for federal agencies has
passed. If you have not patched and checked for compromise indicators, do both
now.
Affected and fixed versions
Fixed releases: 7.1.2, 7.0.6, 6.9.9, 6.8.10, with backports available as far back as the 4.7 branch. If you are on anything older than the fixed release for your branch, you are exposed.
What to do right now
- Update immediately to the fixed release for your branch.
- Check for compromise before and after patching. Patching does not remove
an existing backdoor. Look for:
- Unknown administrator users
- Rogue PHP files, including
wp-pear-rce-flag.php,poc87902.php,luci_<random>.php, andzeta_<random>.php - Abuse of
pearcmd.php
- Rotate salts, force password resets, and review access logs for the window before you patched.
This is exactly the class of flaw ZeroBreach’s recurring scans are built to catch: a critical core CVE, a branch-appropriate patch, and a post-patch compromise check, on a schedule, not when you remember.