1-minute read
What a defender needs to know
Pantheon says its infrastructure recorded more than 45 million attempts to exploit wp2shell from nearly 150,000 network sources during the first week after disclosure. The total measures requests, not compromised sites: Pantheon saw WordPress-specific patterns hit Drupal systems, while F5 proved a complete payload from only one address in its own batch-endpoint dataset.
The chain joins CVE-2026-63030 batch-route confusion with CVE-2026-60137 SQL injection to reach unauthenticated WordPress code execution. Wiz observed successful exploitation followed by persistent webshell installation. WordPress released minimum fixes in 7.0.2, 6.9.5, and 6.8.6; current releases 7.1, 7.0.4, 6.9.7, and 6.8.8 supersede those minimums.
Inventory exposed WordPress instances and verify the production-reported core version. Search /wp-json/batch/v1, the rest_route variants, nested requests carrying author_exclude, HTTP 207 or 200 Multi-Status responses, and user agents containing wp2shell or rezwp2shell. Review new plugins, administrators, PHP files, process activity, and outbound connections for every site that was exposed on an affected build.
The expected current-state result is a superseding release and rejection of a benign unauthenticated nested batch request before the inner query handler. That test confirms the present control. Historical logs and host evidence must account for the earlier exposure window.