wp-mass-recon

Batch scan domains for WordPress vulnerabilities and generate prioritized reports.

1.1k|191|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/uphiago/recon-skills --skill wp-mass-recon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wp-mass-recon
Source: https://github.com/uphiago/recon-skills/tree/main/recon/wp-mass-recon
Command: npx skills add https://github.com/uphiago/recon-skills --skill wp-mass-recon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manually scanning large lists of domains for WordPress-specific vulnerabilities is extremely time-consuming and prone to missed findings, especially when performing sector-wide recon or triaging targets from subdomain enumeration tools.

Core Features & Use Cases

  • Parallel batch scanning for WordPress presence, REST API user enumeration, CORS credential reflection, XMLRPC exposure, open registration, and sensitive file leaks across dozens to hundreds of domains.
  • Proven on 600+ US SMB targets across 28 sectors, with built-in false positive filters for SPA catch-all responses and workarounds for common WAF and rate limiting blocks.
  • Use cases include sector-wide vulnerability mapping, triaging large target lists from subfinder or crt.sh, and maximizing findings per minute for red team engagements.

Quick Start

Use the wp-mass-recon skill to scan a list of target domains stored at /root/output/targets.txt and generate a prioritized report of confirmed WordPress vulnerabilities and exposed sensitive files.

Frequently Asked Questions about wp-mass-recon

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I batch scan hundreds of WordPress domains for vulnerabilities?

Batch scanning WordPress vulnerabilities across many domains requires a tool like wp-mass-recon to run parallel checks for user enumeration, CORS reflection, XMLRPC exposure, open registration, and sensitive file leaks. It uses 20 parallel workers for high throughput.

What WordPress security vulnerabilities should I look for during mass recon?

During WordPress mass recon, you should look for REST API user enumeration, CORS credential reflection, XMLRPC exposure, open registration, and sensitive file leaks. These vulnerabilities are commonly triaged to map sector-wide exposure.

Can I triage subdomain enumeration outputs for WordPress vulnerabilities?

Yes, you can triage target lists from subdomain enumeration tools like subfinder or crt.sh. The tool performs live host discovery and WordPress detection to maximize vulnerability discovery throughput for large target sets.

Does WordPress mass recon work against WAF and rate limiting blocks?

WordPress mass recon includes built-in workarounds for common WAF and rate limiting blocks. It also applies false positive filters specifically designed for SPA catch-all responses to ensure accurate vulnerability scoring.

What dependencies do I need to run WordPress vulnerability scanning at scale?

Running WordPress vulnerability scanning at scale requires curl, httpx, and python3 installed in your environment. These dependencies facilitate live host discovery, WordPress detection, and parallel vulnerability checks across target lists.

Why does my WordPress vulnerability scan report false positives on SPA sites?

False positives on SPA sites occur because catch-all responses mimic vulnerable endpoints. WordPress mass recon applies built-in false positive filters to detect and exclude these SPA catch-all responses during vulnerability scoring.