Vigilbase CVEConnect your agent

WordPress Core Interpretation Conflict Vulnerability

Exploited · KEV 2026-07-21Metasploit moduleCVE-2026-63030CWE-436

Exploited since 2026-07-21. 3 of 8 rule sources name it; Cloudflare blocks by default. Our CRS test: not blocked. 1 public exploit repo.

Edge rules
3/8
Our test
Not blocked
CVSS
9.8
EPSS
10.6% Top 4%
Posts, 14d
12026-10-20: 0 posts2026-10-21: 0 posts2026-10-22: 0 posts2026-10-23: 0 posts2026-10-24: 0 posts2026-10-25: 0 posts2026-10-26: 0 posts2026-10-27: 0 posts2026-10-28: 0 posts2026-10-29: 0 posts2026-10-30: 0 posts2026-10-31: 0 posts2026-11-01: 0 posts2026-11-02: 1 posts
Published
2026-07-17
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… More

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.

Ask Vigil

AI · answers from this page
Ask about CVE-2026-63030: who's covered, what to patch first, how vendors compare. I cite sources and won't help with attacks.

Workers AI (Llama 3.3). Can be wrong: check the cited source.

Severity, decoded

CVSS 3.1
Critical · 9.8 / 10

Exploitable over the network, with no privileges and no user interaction, leading to full loss of confidentiality, integrity and availability.

Over the internetNo login neededNo user actionWorks reliablyFull compromise
How the score is built8 metrics
  • Attack vectorAn attacker can reach it over the internet; no access to your network needed.
    Network
  • Attack complexityNo special conditions are needed; the attack works reliably.
    Low
  • Privileges requiredNo account or login is needed.
    None
  • User interactionNo one has to click or open anything; the attack works on its own.
    None
  • ScopeThe damage stays within the vulnerable component.
    Unchanged
  • Confidentiality impactAn attacker can read all data the affected component holds, or the most sensitive parts of it.
    High
  • Integrity impactAn attacker can change any data or files the affected component protects.
    High
  • Availability impactAn attacker can take the component down completely or keep it from serving anyone.
    High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CISA's assessmentSSVC, from the CVE record
ExploitationActive

Attackers are exploiting this in the wild.

AutomatableYes

Attackers can script the attack end to end and hit many targets at once.

Technical impactTotal

A successful attack gives full control over the affected software or all of its data.

Public exploits

4 found
2 Metasploit0 Exploit-DB1 Scanner template1 GitHub PoCs

Links are to third-party code: never run it outside an isolated lab.

Timeline

  1. 2026-07-17
    CVE published
    CVE List
  2. 2026-07-17
    Metasploit module published
    WordPress Core wp2shell Unauthenticated SQL Injection via REST Batch Route Confusion
  3. 2026-07-21
    Added to CISA KEV
    Confirmed exploitation in the wild
  4. 2026-07-21
    Cloudflare rule names it
    Earliest entry we can see is an update
  5. 2026-09-16
    F5 ships a rule
    WordPress REST API Authorization Bypass
  6. 2026-11-02
    First public exploit repository
    l-i-uqing/CVE-2026-63030-wp2shell-repro: WordPress REST Batch route confusion + SQLi RCE chain reproduction (CVE-2026-63030 & CVE-2026-60137)
  7. 2026-11-02
    First social mention we saw
  8. 2026-11-02
    Our test: OWASP Core Rule Set let it through
    paranoia level 1, anomaly threshold 5, default CRS settings
  9. 2026-11-02
    Our test: OWASP Core Rule Set let it through
    paranoia level 2, anomaly threshold 5, default CRS settings

Social

2026-10-20: 0 posts2026-10-21: 0 posts2026-10-22: 0 posts2026-10-23: 0 posts2026-10-24: 0 posts2026-10-25: 0 posts2026-10-26: 0 posts2026-10-27: 0 posts2026-10-28: 0 posts2026-10-29: 0 posts2026-10-30: 0 posts2026-10-31: 0 posts2026-11-01: 0 posts2026-11-02: 1 posts

Exploit repos · unvetted, don't run

  • l-i-uqing·

    l-i-uqing/CVE-2026-63030-wp2shell-repro: WordPress REST Batch route confusion + SQLi RCE chain reproduction (CVE-2026-63030 & CVE-2026-60137)

    View on GitHub

Vendor statements

Quoted
CloudflareWAF Managed Rules2 quotesBlocks by default

Named by 2026-07-21; the first entry is an update, so the rule may be older.

2026-07-21Updated…550664b6Default: BlockSource
Wordpress - Remote Code Execution - CVE:CVE-2026-63030. Previous action: N/A. New action: Block. This was labeled as Generic Rules - Unauthenticated RCE.
2026-07-21Updated…b5ec246aDefault: BlockSource
Wordpress - Remote Code Execution - CVE:CVE-2026-63030. Previous action: N/A. New action: Block. This was labeled as Generic Rules - Unauthenticated RCE.
AWSAWS WAF Managed RulesNo public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. AWS often describes a vulnerability without naming its CVE (for example "Log4j"). We count only entries that name the CVE, so AWS coverage is understated.

Microsoft AzureFront Door and Application Gateway WAF (DRS)2 quotesRule published
UndatedListed99001019Source
Rule 99001019: Critical - 5 · 2 · Attempted WP2Shell remote code execution exploitation CVE-2026-63030
UndatedListed800116Source
Rule 800116: Critical - 5 · PL2 · Attempted WP2Shell remote code execution exploitation CVE-2026-63030
Google CloudCloud Armor preconfigured WAF rulesNo public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Google names few CVEs: the release notes start in May 2024 and the rules reference lists CVEs without dates. Its cve-canary rules are opt-in.

FastlyNext-Gen WAF virtual patchesBefore feed history

The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.

F5Attack signatures (Distributed Cloud WAF)1 quoteRule published

First rule 2026-09-16, 61 days after the CVE was published.

2026-09-16New rule200013195Source
Added: signature 200013195 "WordPress REST API Authorization Bypass" (Authentication/Authorization Attacks, risk High), systems: WordPress. References: CVE-2026-63030, CVE-2026-60137.
AkamaiApp & API Protector (Adaptive Security Engine)No public source

This vendor publishes no machine-readable rule changelog we can check.

OWASP CRSCore Rule Set (open source, used inside many WAFs)No public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. CRS rarely names CVEs: it relies on generic detections. Our own lab measures what it actually blocks.