WordPress Core Interpretation Conflict Vulnerability
WordPress — WordPress
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.
9.8
8.9%
Vector breakdown
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- Jul 17, 2026
- Modified
- Jul 22, 2026
- Added to KEV
- Jul 21, 2026
- Federal patch due
- Jul 24, 2026
CISA required action
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Weakness classification
Proof-of-concept & exploitation references
8 foundWeaponization
Public repositories whose name or description references CVE-2026-63030, found via a live GitHub search at request time. These are community-sourced signals, not a verified working exploit - cross-check each one before relying on it, and treat higher star counts and recent activity as (weak) corroboration, not proof.
- Icex0/wp2shell-poc★ 479
wp2shell (CVE-2026-63030 & CVE-2026-60137) - full RCE chain
updated Jul 22, 2026
- 0xsha/wp2shell★ 58
CVE-2026-63030 + CVE-2026-60137 - “wp2shell”: unauthenticated RCE in WordPress core
updated Jul 22, 2026
- dinosn/wp2shell-lab★ 36
Non-destructive detector + Docker lab for wp2shell (CVE-2026-63030 REST /batch/v1 route confusion + CVE-2026-60137 author__not_in SQLi) in WordPress core 6.9.0-6.9.4 / 7.0.0-7.0.1
updated Jul 22, 2026
- ZephrFish/wp2shell-scanner★ 21
CVE-2026-63030, CVE-2026-60137, wp2shell scanner
updated Jul 22, 2026
- 47Cid/wp2shell-lab★ 13
Educational PoC + lab for CVE-2026-63030 + CVE-2026-60137: pre-auth SQLi in WordPress core via REST batch-route confusion
updated Jul 22, 2026
- NULL200OK/WP2Shell★ 9
WP2Shell - CVE-2026-63030 / CVE-2026-60137 This tool exploits a critical SQL injection vulnerability in the WordPress REST API `/wp-json/batch/v1` endpoint, allowing unauthenticated attackers to execute arbitrary SQL queries and achieve Remote Code Execution (RCE) on vulnerable WordPress installations.
updated Jul 21, 2026
- 4minx/CVE-2026-63030★ 8
CVE-2026-63030 (wp2shell) POC.
updated Jul 20, 2026
- codeb0ssx/Ultimate-wp2shell★ 8
wp2shell — Pre-authentication RCE in WordPress Core (CVE-2026-60137 + CVE-2026-63030). Chains an SQL injection in author__not_in with batch-route confusion for unauthenticated remote code execution on WP 6.9.0–6.9.4 / 7.0.0–7.0.1.
updated Jul 20, 2026
References
Frequently asked questions
What is CVE-2026-63030?
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.
How severe is CVE-2026-63030?
CVE-2026-63030 has a CVSS base score of 9.8 out of 10 (CVSS 3.1).
Is CVE-2026-63030 actively exploited in the wild?
Yes. CVE-2026-63030 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added Jul 21, 2026, meaning CISA has confirmed evidence of active exploitation.
What is the EPSS score for CVE-2026-63030?
8.9% - meaning FIRST.org's EPSS model estimates a 8.9% probability this vulnerability will be exploited in the wild within 30 days (95% percentile among all scored CVEs).
Is there exploit tooling available for CVE-2026-63030?
Yes - a public Nuclei template referencing CVE-2026-63030 exist in public repositories we checked. We also found 8 public GitHub repositories referencing this CVE.
What type of vulnerability is CVE-2026-63030?
CVE-2026-63030 is classified under CWE-436 (CWE-436 Interpretation Conflict).
Cross-checked against
Impactr finds and proves whether CVE-2026-63030 - or flaws like it - are actually reachable in your own web apps and APIs, with a reproducible exploit as evidence.
Join the waitlist