'WP2Shell' Opens Millions of WordPress Sites to Remote Takeover
Vulnerability: Attackers exploit WP2Shell to remotely compromise WordPress sites via chained SQLi and RCE vulnerabilities.
Deep Analysis and Expert Commentary
The WP2Shell exploit chain combines CVE-2026-60137, an SQL injection flaw requiring authentication, with CVE-2026-63030, a logic flaw in WordPress's Batch REST API that bypasses authentication. This allows attackers to execute arbitrary code on vulnerable systems. The attack path begins with manipulating database queries to escalate privileges, followed by deploying malicious plugins for persistent access. The sheer scale of WordPress's install base amplifies the impact, with tens of thousands of exploitation attempts already observed. Mitigation requires immediate patching, auditing for unauthorized admin accounts, and monitoring for anomalous API requests. Organizations should also restrict batch API usage where possible.
Action Items
- Patch WordPress installations immediately to address CVE-2026-60137 and CVE-2026-63030.
- Audit WordPress instances for new administrator accounts or suspicious plugins.
- Monitor REST API logs for unusual batch request patterns.
Original Article Brief Intro
Dark Reading · 2026-07-20 · Vulnerability: Attackers exploit WP2Shell to remotely compromise WordPress sites via chained SQLi and RCE vulnerabilities.
Related Terms and Notes
CVE IDs
- CVE-2026-60137 — SQL injection vulnerability in WordPress Core allowing authenticated database manipulation.
- CVE-2026-63030 — Logic flaw in WordPress's Batch REST API enabling unauthenticated request execution.
Techniques / TTPs
- RCE
- SQL Injection
Context Notes
- Remote Code Execution
- SQLi
- WordPress
- WP2Shell