WordPress 6.9.x before 6.9.5 and 7.0.x before 7.0.2 is affected by a REST API batch endpoint route confusion issue which, combined with the author__not_in WP_Query SQL Injection (CVE-2026-60137), could allow an attacker to perform SQL Injection and achieve Remote Code Execution.
Severity
CVSS 3.1
9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
11%(unchanged from 11% a week ago; 11% 30 days ago) estimated probability of exploitation activity in the next 30 days; 96th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2026-07-21, due 2026-07-24
CISA's assessment (SSVC)
Exploitation: active · Automatable: yes · Technical impact: total, assessed 2026-07-22. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Show the promptExplain CVE-2026-63030 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-63030?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-63030?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-63030 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
Icex0/wp2shell-pocHarbor Check: matches CVE812 stars, created wp2shell (CVE-2026-63030 & CVE-2026-60137) - full RCE chain
0xsha/wp2shellHarbor Check: matches CVE124 stars, created CVE-2026-63030 + CVE-2026-60137 - “wp2shell”: unauthenticated RCE in WordPress core
ZephrFish/wp2shell-scannerHarbor Check: matches CVE71 stars, created CVE-2026-63030, CVE-2026-60137, wp2shell scanner
dinosn/wp2shell-labHarbor Check: matches CVE67 stars, created Non-destructive detector + Docker lab for wp2shell (CVE-2026-63030 REST /batch/v1 route confusion + CVE-2026-60137 author__not_in SQLi) in …
securelayer7/WordPresShellHarbor Check: matches CVE20 stars, created Pre-auth RCE PoC for CVE-2026-63030 / CVE-2026-60137 (WordPress core)
45 more
mcipekci/wp2shellHarbor Check: matches CVE18 stars, created Pre-auth RCE PoC for WordPress core — chains CVE-2026-63030 (REST /batch/v1 route-confusion desync) with CVE-2026-60137 (author__not_in SQL…
NULL200OK/WP2ShellHarbor Check: matches CVE17 stars, created WP2Shell - CVE-2026-63030 / CVE-2026-60137 This tool exploits a critical SQL injection vulnerability in the WordPress REST API `/wp-json/ba…
47Cid/wp2shell-labHarbor Check: matches CVE15 stars, created Educational PoC + lab for CVE-2026-63030 + CVE-2026-60137: pre-auth SQLi in WordPress core via REST batch-route confusion
4minx/CVE-2026-63030Harbor Check: matches CVE11 stars, Python, created CVE-2026-63030 (wp2shell) POC.
J4ck3LSyN-Gen2/CVE-2026-63030-wp2r00tHarbor Check: matches CVE10 stars, Python, created A fully red-team(offensive security) weaponized variant of wp2shell, built for authorized penetration testing & educational purposes.
fullhunt/wp2shell-scanHarbor Check: matches CVE6 stars, created A scanner and proof-of-concept toolkit for CVE-2026-63030 (wp2shell) - pre-authenticated remote code execution in WordPress core
mverschu/CVE-2026-63030Harbor Check: matches CVE5 stars, Python, created PoC Exploit of WordPress Core Unauthenticated RCE known as WP2Shell
Senanfurkan/wordpress-cve-2026-63030Harbor Check: matches CVE5 stars, Python, created Pre-auth RCE in WordPress Core via REST API batch route confusion + WP_Query SQLi (CVE-2026-63030 / CVE-2026-60137). Detection PoC.
DeadExpl0it/wp2shell-pocHarbor Check: matches CVE3 stars, created wp2shell — WordPress Core Pre-Auth RCE Chain poc for CVE-2026-63030 and CVE-2026-60137
johnlodan/wp2shell-rceHarbor Check: matches CVE3 stars, created WordPress CVE-2026-63030 and CVE-2026-60137 security tool for detecting exposure to the WP2Shell pre-authentication RCE chain.
Crypto-Cat/wp2shellHarbor Check: matches CVE3 stars, created PoC for CVE-2026-63030 + CVE-2026-60137, AKA WP2Shell
g0d150ne/WP2ShellHarbor Check: matches CVE2 stars, created WP2Shell is a powerful and modular exploit framework that combines two critical WordPress vulnerabilities (CVE-2026-63030 and CVE-2026-6013…
Ch4120N/CVE-2026-63030Harbor Check: matches CVE2 stars, Python, created CVE-2026-63030 - WordPress REST Batch Route-Confusion SQL Injection Proof of Concept
lucifer0xf/wp2shell-Wordpress-TOWNHarbor Check: matches CVE2 stars, created Unauthenticated Remote Code Execution (RCE) in WordPress Core allows attackers to execute arbitrary code without logging in by chaining CVE…
hidden-investigations/wp2shell-scannerHarbor Check: matches CVE1 star, created WordPress wp2shell vulnerability-chain scanner for CVE-2026-63030 and CVE-2026-60137, with active detection, optional PoC, JSON export.
0xWhoknows/wp2shellHarbor Check: matches CVE1 star, created Automated exploit chain for CVE-2026-63030 / CVE-2026-60137 — unauthenticated blind SQLi via WordPress REST batch route-confusion. Dumps us…
Bhanunamikaze/WP2Shell-CVE-2026-63030-POCHarbor Check: matches CVE0 stars, Python, created PoC detector & safe validator for the WP2Shell WordPress vulnerability chain: CVE-2026-63030 (REST batch-route confusion) + CVE-2026-60137 …
Detection rules
Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.