CVE-2026-63030

HIGHPre-NVD 7.59.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-07-21), indicating real-world exploitation has been confirmed by US federal agencies. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5 retained for reference (NVD's own analysis pending). Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa-adp, cisa_kev, epss
Trending — KEV-added this weekExploited in the wild
7.5
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 39%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
9.0(high)
EPSS
98.4%
KEV
⚠ Exploited

Published

July 17, 2026

Last Modified

July 22, 2026

Advisory Details (2)

Auto-updated Jul 17, 2026
Patch available. Sources: github.
generic

WordPress 7.0.2 Release – WordPress News

https://wordpress.org/news/2026/07/wordpress-7-0-2-release/
github Patch Available

REST API batch-route confusion and SQL injection issue leading to Remote Code Execution · Advisory · WordPress/wordpress-develop · GitHub

https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-ff9f-jf42-662q

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 25× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-22 05:22 UTCEG score recompute▼ 0.80
  4. 2026-07-22 05:20 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  5. 2026-07-21 20:14 UTCEG score recompute▲ 0.80
  6. 2026-07-21 20:13 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  7. 2026-07-21 17:19 UTCEG score recompute▼ 0.80
  8. 2026-07-21 17:18 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  9. 2026-07-21 16:01 UTCEG score recompute▲ 0.80
  10. 2026-07-21 15:58 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  11. 2026-07-21 15:25 UTCEPSS rescore
  12. 2026-07-21 15:25 UTCEPSS rescore
  13. 2026-07-21 14:39 UTCEG score recompute▲ 1.50
  14. 2026-07-21 14:37 UTCCISA KEV update
  15. 2026-07-20 17:08 UTCEPSS rescore
  16. 2026-07-19 14:31 UTCEPSS rescore
  17. 2026-07-19 02:29 UTCEPSS rescore
  18. 2026-07-18 06:05 UTCEG score recompute▼ 2.30
  19. 2026-07-18 06:02 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  20. 2026-07-18 04:20 UTCEG score recompute▲ 2.30
  21. 2026-07-18 04:19 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  22. 2026-07-17 20:20 UTCEG score recompute▲ 7.50
  23. 2026-07-17 20:19 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  24. 2026-07-17 19:25 UTCEG score recompute
  25. 2026-07-17 19:24 UTCMITRE cvelistV5first tracked

Publicly available exploits

(10 references)

Working exploit code is in the public domain (10 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCikow/wp2shell
    First seen Jul 19, 2026

    wp2shell — WordPress Core Pre-Auth RCE (CVE-2026-63030 + CVE-2026-60137). Exploit toolkit + remediation.

    Open source ↗
  • GitHub PoCbahartanir/wp2shell-scanner
    First seen Jul 19, 2026

    CVE-2026-63030 / CVE-2026-60137 - WordPress pre-auth RCE scanner

    Open source ↗
  • GitHub PoC47Cid/wp2shell-lab
    First seen Jul 18, 2026

    Educational PoC + lab for CVE-2026-63030 + CVE-2026-60137: pre-auth SQLi in WordPress core via REST batch-route confusion

    Open source ↗
  • GitHub PoC0xsha/wp2shell
    First seen Jul 18, 2026

    CVE-2026-63030 + CVE-2026-60137 - “wp2shell”: unauthenticated RCE in WordPress core

    Open source ↗
  • GitHub PoCNULL200OK/WP2Shell
    First seen Jul 18, 2026

    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.

    Open source ↗
  • GitHub PoCdinosn/wp2shell-lab
    First seen Jul 18, 2026

    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

    Open source ↗
  • GitHub PoCSenanfurkan/wordpress-cve-2026-63030
    First seen Jul 18, 2026

    Pre-auth RCE in WordPress Core via REST API batch route confusion + WP_Query SQLi (CVE-2026-63030 / CVE-2026-60137). Detection PoC.

    Open source ↗
  • GitHub PoCekomsSavior/wp2shell
    First seen Jul 18, 2026

    CVE-2026-63030 (RCE) + CVE-2026-60137 (SQLi)

    Open source ↗
  • GitHub PoCmhtsec/CVE-2026-63030
    First seen Jul 18, 2026

    WordPress 未授权RCE EXP | CVE-2026-63030

    Open source ↗
  • GitHub PoC4minx/CVE-2026-63030
    First seen Jul 18, 2026

    CVE-2026-63030 (wp2shell) POC.

    Open source ↗

Related CVEs(same CWE)

Frequently asked(6)

What is CVE-2026-63030?
CVE-2026-63030 is a high vulnerability published on July 17, 2026. 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 authornotin WPQuery SQL Injection (CVE-2026-60137), could allow an attacker to perform SQL Injection and achieve Remote Code Execution.
When was CVE-2026-63030 disclosed?
CVE-2026-63030 was first published in the National Vulnerability Database on July 17, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63030 actively exploited?
Yes. CISA added CVE-2026-63030 to the Known Exploited Vulnerabilities catalog on July 21, 2026, affecting WordPress Core. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2026-63030?
CVE-2026-63030 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
Which products are affected by CVE-2026-63030?
CVE-2026-63030 affects WordPress Core. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2026-63030?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63030, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-63030

Explore →

Is Your Infrastructure Affected by CVE-2026-63030?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs