cbcvebase.
CVE-2026-63030
published 2026-07-17

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…

PriorityP198critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
KEVITWEXPLOITInitial access
CISA Known Exploited Vulnerabilitydue 2026-07-24
Exploited in the wild
EPSS
98.05%
99.9th percentile
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.

Affected

3 ranges
VendorProductVersion rangeFixed in
wordpresswordpress< 7.0.27.0.2
wordpresswordpress>= 6.9 < 6.9.56.9.5
wordpresswordpress>= 7.0 < 7.0.27.0.2

Detection & IOCsextracted from sources · hover to see the quote

url/wp-json/batch/v1 (REST API batch endpoint)
  • Monitor for unauthenticated requests to the WordPress REST API batch endpoint (e.g., /wp-json/batch/v1) that include query parameters consistent with WP_Query author__not_in manipulation, which is the chained SQL injection vector (CVE-2026-60137).
  • The vulnerable code path can be reached when a persistent object cache is NOT in use on the WordPress installation — prioritize detection and patching on sites without persistent object caching.
  • No authentication, plugins, or user interaction are required to exploit this vulnerability — treat any anomalous unauthenticated REST API batch requests as high-priority alerts.
  • Affected WordPress versions are 6.9.0–6.9.4 and 7.0.0–7.0.1; fingerprint version strings in HTTP responses or /wp-includes/version.php to identify unpatched instances.
  • CVE-2026-63030 is chained with CVE-2026-60137 (author__not_in WP_Query SQL Injection / GHSA-fpp7-x2x2-2mjf); detection rules should account for both the route confusion trigger and the SQL injection payload in the same request flow.
  • ·The exploit chain only works when a persistent object cache is absent. WordPress sites with a persistent object cache (e.g., Redis, Memcached) are not reachable via this vulnerable code path, which should be factored into risk prioritization.
  • ·WordPress versions prior to 6.8 are not affected by either CVE-2026-63030 or CVE-2026-60137; WordPress 6.8.x is only affected by CVE-2026-60137 (the SQL injection component), not the RCE chain.

CVSS provenance

nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vulncheck9.1CRITICAL
cisa5.9MEDIUM
CVEs like this are exactly what “Exploited This Week” covers.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.