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.
The record classifies CVE-2026-63030 under weakness class CWE-436. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 89 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 9.8 — CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - EPSS (FIRST)
- 38.5% probability of exploitation in the next 30 days, higher than 98.4% of all scored CVEs
- CISA KEV
- Listed since 2026-07-21, federal remediation deadline 2026-07-24
- Threadlinqs priority
- 9/10 — CISA KEV-listed, which Threadlinqs floors at 9
- Published
- 2026-07-17, last modified 2026-07-22
Is CVE-2026-63030 being exploited?
CISA added CVE-2026-63030 to the Known Exploited Vulnerabilities catalog on 2026-07-21, which means the agency holds evidence of exploitation in the wild; US federal civilian agencies had to remediate it by 2026-07-24 under BOD 22-01. Weaponised exploit code for CVE-2026-63030 is publicly available. 10 public proof-of-concept repositories are tracked for this identifier. A ProjectDiscovery Nuclei detection template exists (http/cves/2026/CVE-2026-63030.yaml). It currently carries a trending score of 88 in the Threadlinqs vulnerability feed.
- Icex0/wp2shell-poc (github)
- 0xsha/wp2shell (github)
- dinosn/wp2shell-lab (github)
- ZephrFish/wp2shell-scanner (github)
- 47Cid/wp2shell-lab (github)
- NULL200OK/WP2Shell (github)
- mcipekci/wp2shell (github)
- 4minx/CVE-2026-63030 (github)
Affected products and versions
- WordPress: WordPress
How to fix CVE-2026-63030
Vendor advisory: https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-ff9f-jf42-662q. Because CVE-2026-63030 is KEV-listed, US federal civilian agencies were required to apply the vendor fix, or stop using the product, by 2026-07-24. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.
Threat activity tracking CVE-2026-63030
8 tracked threats in the Threadlinqs corpus reference CVE-2026-63030, either in the campaign’s CVE list or as an indicator on the campaign record.
- September 2026 CVE Landscape: 94 high-impact vulnerabilities, NetScaler zero-days CVE-2026-88771/CVE-2026-88772, AI-agent-assisted exploitation — CRITICAL · 2026-10-14
- CyberXero: AI-Augmented Initial Access Broker Targeting Ukrainian Critical Infrastructure and Global WordPress/E-commerce Platforms — HIGH · 2026-10-07
- TIKTOUK Toolkit Harvests AWS, SMTP and Database Credentials from Exposed WordPress Backups and Config Files (CVE-2026-60137, CVE-2026-63030) — HIGH · 2026-10-04
- Chinese-Speaking 'Kapibala' Actor (Red Heron-Linked) Chains WordPress wp2shell, Zyxel GS1900, and Ubiquiti UniFi OS Flaws to Steal Government Data — CRITICAL · 2026-09-22
- AI-Agent-Driven Offensive Operation: Mass Cryptocurrency Wallet and Credential Compromise via Autonomous AI Coding Agents — CRITICAL · 2026-08-19
- wp2shell RCE Chain in WordPress Core (CVE-2026-60137, CVE-2026-63030) — Emergency Patch Released — CRITICAL · 2026-07-18
- wp2shell: WordPress Core REST API Batch-Route Confusion Chained with author__not_in SQL Injection (CVE-2026-63030 / CVE-2026-60137) Yields Unauthenticated Pre-Auth RCE — CRITICAL · 2026-07-17
- CVE-2026-63030 (wp2shell): Unauthenticated Remote Code Execution in WordPress Core REST API Batch Endpoint via Chained SQL Injection (CVE-2026-60137) — CRITICAL · 2026-07-17
Sources
Enriched from CVE.org, NVD, FIRST EPSS, CISA KEV, public proof-of-concept repositories, ProjectDiscovery Nuclei. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.