explaingit

j4ck3lsyn-gen2/cve-2026-63030-wp2r00t

Analysis updated 2026-05-18

5PythonAudience · researcherComplexity · 3/5LicenseSetup · easy

TLDR

A safety gated proof of concept tool demonstrating a WordPress REST API SQL injection vulnerability (CVE-2026-63030) for authorized security research.

Mindmap

mindmap
  root((wp2r00t PoC))
    What it does
      Demonstrates WordPress SQLi
      Route confusion bug
      CVE-2026-63030
    Safety gates
      Authorized flag required
      Noop dry run mode
      Request budget cap
    Use cases
      Confirm vulnerability
      Extract data safely
      Study mitigation steps
    Audience
      Security researchers
      Pentesters

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Confirm whether a WordPress site is vulnerable to CVE-2026-63030 in an authorized test

USE CASE 2

Study how a route confusion bug in a REST batch endpoint leads to SQL injection

USE CASE 3

Practice safe, gated penetration testing workflows with explicit authorization flags

USE CASE 4

Preview exploit payloads in no-network dry run mode before running against a lab target

What is it built with?

Python

How does it compare?

j4ck3lsyn-gen2/cve-2026-63030-wp2r00t1ncendium/aibusteraaronmayeux/ha-hurricane-tracker
Stars555
LanguagePythonPythonPython
Setup difficultyeasymoderateeasy
Complexity3/53/52/5
Audienceresearcherops devopsgeneral

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

Standard library only, requires Python 3.11+ and an explicit --authorized flag before it will contact any real target.

MIT license: free to use, modify, and distribute, including commercially, as long as the copyright notice is kept.

In plain English

This repository is a proof of concept tool for security researchers studying a specific WordPress vulnerability, CVE-2026-63030. It demonstrates a SQL injection flaw found in WordPress's REST API batch endpoint, the part of WordPress that lets multiple API requests be bundled and sent together. The author built this independently based on the public vulnerability details, and it targets WordPress versions before 6.9.5 and 7.0.2, which have since been patched. The README explains the underlying bug in detail: when the batch endpoint processes several sub-requests at once, a validation mistake can cause one sub-request to be handled by the wrong code path. By nesting this confusion twice, an attacker can eventually reach a spot where a value gets inserted directly into a database query without being checked, which is the classic definition of a SQL injection flaw. This allows an unauthenticated attacker to extract information from the site's database. The tool is built with safety in mind. It requires an explicit authorized flag before it will contact any real target, and it includes a no operation mode that only shows what it would send without actually sending anything. There is also a hard limit on the number of requests it will make. A separate flag called r00t gates any post authentication capability, meaning the more dangerous features cannot run without it. The author states plainly that a further weaponized persistence tool, used for maintaining long term access after a break in, was deliberately left out of this public repository due to legal concerns. It runs on Python 3.11 or newer with no external dependencies, and is operated entirely through a command line interface with modes for checking, reading data, and a gated post authentication shell. The author is explicit that this is meant strictly for authorized penetration testing and educational research in isolated lab environments, not for use against systems the user does not own or have permission to test.

Copy-paste prompts

Prompt 1
Explain step by step how the route confusion bug in wp2r00t leads to SQL injection.
Prompt 2
Walk me through running poc.py in --noop mode to preview the check payloads safely.
Prompt 3
What do the --authorized and --max-requests flags protect against in this tool?
Prompt 4
Summarize the mitigation steps I should apply to a WordPress site vulnerable to CVE-2026-63030.

Frequently asked questions

What is cve-2026-63030-wp2r00t?

A safety gated proof of concept tool demonstrating a WordPress REST API SQL injection vulnerability (CVE-2026-63030) for authorized security research.

What language is cve-2026-63030-wp2r00t written in?

Mainly Python. The stack also includes Python.

What license does cve-2026-63030-wp2r00t use?

MIT license: free to use, modify, and distribute, including commercially, as long as the copyright notice is kept.

How hard is cve-2026-63030-wp2r00t to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is cve-2026-63030-wp2r00t for?

Mainly researcher.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.