Attackers are now actively exploiting the “wp2shellaaaa” remote code execution (RCE) vulnerability chain in unpatched WordPress sites, escalating the threat against millions of websites that have not yet applied emergency security updates. The critical flaw, which combines a pre-authentication SQL injection with a route confusion bug to achieve full site takeover, was discovered with the assistance of an advanced AI model, marking a significant moment for both offensive security research and the escalating risk for site administrators.
Security firm Patchstack has confirmed it is already observing live exploitation attempts in customer logs, advising administrators to treat the situation with the highest urgency. The exploit chain, impacting the WordPress core rather than a third-party plugin, allows an unauthenticated attacker to completely compromise a vulnerable website, create administrative accounts, and deploy malicious plugins.
How the wp2shell Attack Chain Works
The wp2shell exploit leverages two distinct vulnerabilities in the WordPress core. The first, tracked as CVE-2026-63030, is a route-and-handler confusion bug in the REST API batch endpoint. A malformed request can cause WordPress to validate one sub-request against the wrong handler and then execute it using another, breaking the normal link between validation, permissions, and dispatch. The second issue, CVE-2026-60137, is an SQL injection condition in WP_Query. A parameter used to exclude author IDs is sanitized when passed as an array, but not when supplied as a scalar value.
Under normal processing, WordPress validation prevents that unsafe input from reaching the query layer. The batch-route confusion bypasses those checks and exposes the injection to unauthenticated attackers. The AI-generated exploit went further by abusing WordPress’s in-memory post cache, oEmbed cache rows, theme customization changesets, post-parent cycle handling, and dynamically generated hooks. This allowed the attacker to temporarily assume an administrator’s identity, replay the original REST request with elevated privileges, create a new administrator account, and then upload a malicious plugin to execute code.
AI-Assisted Discovery and the Changing Threat Landscape
Adam Kues, a security researcher at Searchlight Cyber, discovered the wp2shell chain by directing a GPT-5.6 Sol Ultra model to audit a clean copy of the latest stable WordPress source code. Kues adapted a multi-agent research prompt originally designed for solving complex mathematical problems, instructing the model to avoid changelogs and internet-based patch comparisons, and asking it to search specifically for a realistic pre-authentication route to code execution. The work took just over 10 hours of model runtime and cost roughly $25 based on a prorated usage of a $200 subscription. This development underscores a rapidly evolving threat landscape where AI is lowering the barrier to discovering complex, chained vulnerabilities in widely-used software.
What is the Impact of the WordPress wp2shell Vulnerability?
For site owners, the primary risk is complete, unauthenticated takeover. An attacker does not need a password or any prior access to the WordPress dashboard. The exploit chain provides direct access to execute arbitrary PHP code, which can be used to deface the site, steal sensitive data from the database, inject malicious content for site visitors, or use the compromised server for further attacks. Given that WordPress powers a substantial portion of the web, the potential for widespread exploitation is significant.
Which WordPress Versions Are Affected and Patched?
WordPress has released emergency updates to address these flaws. Users must update immediately to version 7.0.2, 6.9.5, or 6.8.6, depending on their current branch. Any site running an older version is considered vulnerable and at high risk of compromise.
What Affected Administrators Should Do Now
Administrators should treat the situation as an active, ongoing threat and take the following steps immediately. First, confirm that WordPress has been updated to the latest patched version for your branch. Second, audit user accounts, paying close attention to any unfamiliar administrator-level accounts. Third, review recently installed plugins for anything suspicious. Fourth, check for modified PHP files, particularly in the themes and plugins directories. Fifth, inspect web server logs for unusual request patterns, especially those targeting the REST API batch endpoint. Finally, monitor outbound connections from the web server for signs of command-and-control (C2) communication or data exfiltration. For organizations managing multiple sites, it is critical to inventory all WordPress installations and ensure compliance with the patch. In addition to these immediate steps, implementing a multilayered security approach that includes web application firewalls (WAF), regular vulnerability scanning, and file integrity monitoring can provide protection against similar emerging threats. The use of a reputable, continuously updated security plugin that provides virtual patching can also mitigate risk for sites that cannot be updated immediately.
