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
WP2Shell-Scanner — Read-only CLI to check whether a WordPress site is exposed to WP2Shell (CVE-2026-63030 / CVE-2026-60137) | Kitploit
Tools/GitHubGitHub/sec-dan/wp2shell-scanner
ReconnaissanceVulnerability ScannersInformation GatheringWeb SecurityPenetration TestingSubdomain Enumeration
GitHubsec-dan/wp2shell-scanner

WP2Shell-Scanner

Read-only CLI to check whether a WordPress site is exposed to WP2Shell (CVE-2026-63030 / CVE-2026-60137)

View Repository
301 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

WP2Shell Scanner

Python CVE-2026-63030 CVE-2026-60137

A command line tool that checks whether a WordPress site is exposed to WP2Shell (CVE-2026-63030 and CVE-2026-60137). It reads the WordPress version and REST API surface over read-only requests and reports a verdict. It does not exploit anything.

[!WARNING] For authorised testing only. Use it on sites you own or have written permission to check. The author (DanSec) takes no responsibility for misuse or damage.

About WP2Shell

WP2Shell chains a SQL injection (CVE-2026-60137) with a REST batch processor flaw (CVE-2026-63030) through the /wp-json/batch/v1 endpoint, giving unauthenticated remote code execution on a default WordPress install. Both CVEs are in CISA's Known Exploited catalog.

BranchVulnerableFixed in
6.9.x6.9.0 through 6.9.46.9.5
7.0.x7.0.0 through 7.0.17.0.2
7.1 and laternot affectedn/a

Install

Requires Python 3.8+.

pip install -r requirements.txt

requests and rich are required. sublist3r is optional (subdomain enumeration). For wider enumeration, install subfinder (a Go binary, not pip) and pass --subfinder.

Usage

# Check one host
python wpScanner.py example.com --passive

# Enumerate subdomains of a root domain and check each one
python wpScanner.py example.com --subfinder --threads 8
OptionDescriptionDefault
-o, --outputCSV output fileWP2Shell_output.csv
--passiveCheck only the given host, skip enumerationoff
--subfinderAdd subfinder as a subdomain sourceoff
--threadsConcurrent workers1
--retriesRetries per host1
--rate-limitMax requests/sec (single-thread, 0 = no limit)0

Results

VerdictMeaning
VULNERABLEAffected version and the batch endpoint is reachable.
LIKELY_MITIGATEDAffected version, but the batch endpoint looks blocked or REST is disabled.
PATCHEDFixed version, or predates the affected releases.
VERSION_UNKNOWNWordPress found, version could not be read.
NOT_WORDPRESSNo WordPress fingerprint.
ERRORUnreachable or network error.

Results are also written to CSV. When version sources disagree, the tool classifies on the lowest one to avoid a false all-clear. A remote check cannot see a backported patch that left the version string unchanged, so on hosts you control, wp core version is the ground truth.

Remediation

Update core to 6.9.5, 7.0.2, or 7.1+ (wp core update). If you cannot patch yet, block /wp-json/batch/v1 at your firewall and restrict anonymous REST access.

Disclaimer

Provided for authorised, defensive use only. You are responsible for having permission to check any host you point it at.

Download Tool