Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
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.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
Tools/GitHubGitHub/githu836/poc-for-cve-2026-63030
Payload GenerationVulnerability AnalysisExploitationWeb Application ExploitationWeb SecurityPenetration TestingRemote Access Tool
GitHubgithu836/poc-for-cve-2026-63030

PoC-for-CVE-2026-63030

Python PoC exploiting a WordPress pre-auth RCE chain (CVE-2026-63030 route confusion + CVE-2026-60137 SQLi) to create admins, dump users, and upload a webshell.

View Repository
28 days agoNot yet reviewed
Share

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

WordPress Pre-Authentication Remote Code Execution Chain


Overview

This script exploits a chain of two vulnerabilities in WordPress:

  1. CVE-2026-63030 — Route confusion in the /wp-json/batch/v1 endpoint, allowing desynchronization of request validation.
  2. CVE-2026-60137 — SQL injection in the author__not_in parameter of the /wp/v2/posts REST API.

When chained, an attacker can create a new administrator account without authentication, then upload a webshell through the WordPress theme editor.

CVSS v3.1: 9.8 (Critical)
Status: Added to CISA KEV Catalog (due date July 24, 2026)
Patched in: WordPress 6.9.5, 7.0.2, 6.8.6


Affected Versions

VersionStatus
6.8.0 – 6.8.5SQLi only (CVE-2026-60137)
6.9.0 – 6.9.4Full RCE chain
7.0.0 – 7.0.1Full RCE chain
6.9.5, 7.0.2, 6.8.6Patched

Requirements

  • Python 3.8 or newer
  • No external dependencies (stdlib only)
  • Network access to the target WordPress instance
  • Target running a vulnerable version

Installation

git clone https://github.com/Githu836/PoC-for-CVE-2026-63030
cd wp2shell
chmod +x wp2shell.py

Usage

  1. Probe Only (Non-Destructive)
python3 wp2shell.py --url https://target.com --check

Checks whether the target is vulnerable without performing exploitation.

  1. Dump User Credentials
python3 wp2shell.py --url https://target.com --dump-users

Extracts usernames and password hashes from the wp_users table via UNION SQL injection.

  1. Command Execution
python3 wp2shell.py --url https://target.com --cmd "id"

Runs the full chain: create admin → upload webshell → execute command.

  1. Interactive Shell
python3 wp2shell.py --url https://target.com --shell

Opens an interactive shell after the webshell is successfully uploaded.

  1. With Proxy
python3 wp2shell.py --url https://target.com --shell --proxy http://127.0.0.1:8080

How It Works

Phase 1: Probe

The script checks the WordPress version from /readme.html or a JavaScript file, then sends a request to /wp-json/batch/v1 to confirm the batch endpoint is accessible. If the response is not rest_no_route, the target is considered vulnerable.

Phase 2: Route Confusion (CVE-2026-63030)

The script sends a batch payload containing two subrequests:

  1. A request with author__not_in containing the SQL injection payload.
  2. A valid request as a "primer" to trigger validation desynchronization.

Because WordPress processes batches in parallel without state synchronization, the validation of the second request is bypassed.

Phase 3: SQL Injection (CVE-2026-60137)

The author__not_in payload is injected into an improperly escaped SQL query. The script uses UNION-based injection to:

· Extract password hashes from wp_users. · Insert a fake row into wp_posts as "seeding" for the oEmbed cache.

Phase 4: Admin Creation

The script leverages customizer changeset re-entrancy to register a new user with the administrator role. If this method fails, an alternative method is used: a batch request with a malformed primer to bypass user creation validation.

Phase 5: Webshell Upload

After logging in as admin, the script:

  1. Retrieves the nonce from /wp-admin/theme-editor.php.
  2. Writes a PHP shell to 404.php of the active theme.
  3. Tests the shell with the id command.

The shell is accessible at:

https://target.com/wp-content/themes/[theme]/404.php?c=id

Code Structure

wp2shell.py
├── class WP2Shell
│   ├── request()           # HTTP wrapper with cookie jar
│   ├── batch_request()     # Send to /wp-json/batch/v1
│   ├── check()             # Probe version + endpoint
│   ├── sqli_sleep()        # Time-based SQLi test
│   ├── extract_data()      # Blind extraction char-by-char
│   ├── dump_users()        # UNION SQLi to dump users
│   ├── create_admin()      # Customizer re-entrancy
│   ├── alt_create_admin()  # Batch bypass alternative
│   ├── upload_shell()      # Theme editor webshell
│   ├── exploit()           # Full chain
│   └── interactive_shell() # Interactive shell
└── main()                  # CLI parser

Indicators of Compromise (IoC)

After successful exploitation, the target will show:

· A new user with the prefix wp2s_ in the wp_users table. · A 404.php file in the theme directory containing . · POST requests to /wp-json/batch/v1 with author__not_in payloads containing SQL characters. · POST requests to /wp-admin/admin-ajax.php?action=customize_save with customized JSON containing wp_user_roles. · Access log entries to /wp-content/themes/[theme]/404.php?c=....


Mitigation

  1. Update WordPress to 6.9.5, 7.0.2, or 6.8.6.
  2. Disable the batch endpoint if not in use:
    add_filter('rest_endpoints', function($endpoints) {
        unset($endpoints['/wp/v2/batch']);
        return $endpoints;
    });
    
  3. Restrict access to /wp-json/ via WAF or .htaccess.
  4. Audit users with the administrator role regularly.
  5. Monitor logs for author__not_in patterns and suspicious batch requests.

Disclaimer

This script is provided for educational purposes and authorized security testing only. Use against systems without written permission is illegal and violates the law. The author is not responsible for any misuse.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    708
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    500
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    398
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    341
  • 5

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    259
  • 6

    antifox

    antifox-ai/antifox

    AI multi-agent autonomous penetration testing platform that runs recon, attack-surface discovery, exploitation validation and evidence-backed report delivery.

    257

Explore all tools

Browse our collection of tools

View all tools →