Hackers are exploiting a critical WordPress flaw just hours after its disclosure, with security researchers uncovering widespread scanning activity by attackers.
The vulnerability, tracked as CVE-2026-87902, has a CVSS v4.0 score of 9.2 or critical and is a path traversal in WordPress core’s page-template resolver.
The flaw permits attackers to send unauthenticated requests that make WordPress include a readable PHP file from outside the active theme directory, which can lead to Remote Code Execution (RCE) under certain server and theme conditions.
The flaw impacts WordPress Core from 4.7.0 up to and including 7.1.1. It was patched by WordPress on Sept. 22, although attackers began probing the flaw hours after the patch was released.
“Traffic against this CVE is now running at more than ten times the volume we saw on the first evening,” security firm Patchstack, which provides vulnerability tracking and security hardening for WordPress plugins, said in an advisory published on Sept. 22 and updated on Sept. 23.
How the attacks escalated
These activities unfolded in three stages, with the attackers first probing for vulnerable WordPress sites. The attackers then included “pearcmd.php” to check whether the PHP Extension and Application Repository (PEAR) was present and whether it would accept command-line arguments.
In the third stage, the attackers switched to a pearcmd command that created files, which Patchstack said pearcmd “will happily use to write a file wherever it is told, with content the attacker controls.”
Early-warning vulnerability intelligence platform Previdian has observed at least 68 exploitation attempts since Wednesday.
“Updating is still the answer, and given stage three it is now urgent. WordPress backported the fix as far as 4.7.37, so every affected branch has a patched release and an older site can take it without a major version jump,” Patchstack said.