Severity: CRITICAL · Priority: P1 — active exploitation of a critical unauthenticated WordPress flaw, escalate on hit
These rules detect attempts to exploit CVE-2026-87902, a critical unauthenticated vulnerability in WordPress Core patched in WordPress 7.1.2 on September 22, 2026. The flaw affects nearly every WordPress installation from version 4.7.0 onward — code vulnerable for almost ten years before disclosure. It allows an unauthenticated attacker to manipulate the value WordPress uses when choosing a page template, causing it to include a readable PHP file outside the active theme's directories. No WordPress account, authentication cookie, administrator interaction, or vulnerable plugin is required for this file-inclusion step. Exploitation began within hours of the patch being published.
A hit on the traversal or pearcmd rules indicates an exploitation attempt against one of your WordPress servers. Confirm whether the targeted site is running WordPress 7.1.2 or later; if not, upgrade immediately. Note that exploitation into full code execution is conditional: the server must also run PHP with register_argc_argv enabled — which is the default in official PHP Docker images and in many cPanel environments running PHP below version 8.5. If the site is unpatched and those conditions are met, assume the attempt may have succeeded and escalate to incident response: check writable directories (/tmp, /var/tmp) for newly written PHP files with names like wp-pear-rce-*.php or luci_*.php, and look for signs of code execution from those locations. Rotating the site's database credentials and any secrets accessible from the web-server account is prudent where compromise cannot be ruled out.