CVE-2026-63030: WordPress Core Interpretation Conflict Vulnerability
CVE-2026-63030 is a critical-severity flaw (CVSS 9.8) affecting wordpress, reported as exploited in the wild. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
Why this priority
- Critical severity
- EPSS top 4%: very likely to be exploited
- Exploited in the wild (CISA KEV)
- Public exploit reference
- Covered by 5 security sources
- CISA SSVC: automatable with total technical impact
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 9.8 (Critical) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 10.6% (top 4%) |
| CISA exploited list | Yes, fix due 2026-07-24 |
| Weakness | CWE-436 |
| Published | 2026-07-17 |
| Last modified | 2026-10-08 |
Last updated 2026-10-08 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Exploited Added to the CISA Known Exploited Vulnerabilities list
- Deadline CISA due date for US federal agencies to patch
- Updated Record last modified
Exact fixes by distribution
Public exploits and detection
Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.
- GitHub PoC: Icex0/wp2shell-poc (807 stars)
- GitHub PoC: gichirimaku/wp2shell-PoC (564 stars)
- GitHub PoC: 0xsha/wp2shell (120 stars)
- Metasploit: WordPress Core wp2shell Unauthenticated SQL Injection via REST Batch Route Confusion
- Metasploit: WordPress WP2Shell REST API Batch Route Confusion SQLi to RCE
- Nuclei scan template: WordPress Core 6.9-7.0.1 - Pre-Auth Batch-Route Confusion
Advisories and coverage
Official advisories
- F5 Security Advisories: CVE-2026-63030 and CVE-2026-60137: 'wp2shell' Captured Exploit Payload 2026-08-08
- IPA Japan Security Alerts: WordPressの脆弱性対策について(CVE-2026-60137、CVE-2026-63030:wp2shell) 2026-07-21
- CERT-FR Alerts: Multiples vulnérabilités dans WordPress (20 juillet 2026) 2026-07-20
Research and news
- Wiz Research: Exploitation in the Wild of wp2shell 2026-07-20
- VulnCheck Blog: WP2Shell Vulnerabilities: CVE-2026-60137 and CVE-2026-63030 2026-07-17
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-63030?
wordpress: upgrade to 6.9.5, 7.0.2. Exact commands for each OS are on this page.
Is CVE-2026-63030 being exploited?
Yes. CVE-2026-63030 is on the CISA Known Exploited Vulnerabilities list, so treat it as patch-now.
What does CVE-2026-63030 affect?
CVE-2026-63030 affects wordpress. Severity is critical (CVSS 9.8). 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 Injec
How urgent is CVE-2026-63030?
Priority 99/100. Critical severity; EPSS top 4%: very likely to be exploited; Exploited in the wild (CISA KEV); Public exploit reference; Covered by 5 security sources; CISA SSVC: automatable with total technical impact; Remotely exploitable, no login, no user action
Software pages
Related CVEs
- CVE-2026-60137 MEDIUM 5.9 EXPLOITED UPGRADE WordPress Core SQL Injection Vulnerability
- CVE-2026-87902 HIGH 8.1 EXPLOITED UPGRADE WordPress Core Remote File Inclusion Vulnerability