j4ck3lsyn-gen2/cve-2026-63030-wp2r00t — explained in plain English
Analysis updated 2026-05-18
Confirm whether a WordPress site is vulnerable to CVE-2026-63030 in an authorized test
Study how a route confusion bug in a REST batch endpoint leads to SQL injection
Practice safe, gated penetration testing workflows with explicit authorization flags
Preview exploit payloads in no-network dry run mode before running against a lab target
| j4ck3lsyn-gen2/cve-2026-63030-wp2r00t | 1ncendium/aibuster | aaronmayeux/ha-hurricane-tracker | |
|---|---|---|---|
| Stars | 5 | 5 | 5 |
| Language | Python | Python | Python |
| Setup difficulty | easy | moderate | easy |
| Complexity | 3/5 | 3/5 | 2/5 |
| Audience | researcher | ops devops | general |
Figures from each repo's GitHub metadata at analysis time.
Standard library only, requires Python 3.11+ and an explicit --authorized flag before it will contact any real target.
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.
A safety gated proof of concept tool demonstrating a WordPress REST API SQL injection vulnerability (CVE-2026-63030) for authorized security research.
Mainly Python. The stack also includes Python.
MIT license: free to use, modify, and distribute, including commercially, as long as the copyright notice is kept.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly researcher.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.