wp-plugin-cve-hunt

Identify exploitable WordPress plugin CVEs across target domains via version extraction and database cross-referencing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual WordPress plugin CVE research is slow and error-prone, with version information often hidden across multiple sources and CVE data scattered across disparate databases, leading to missed critical vulnerabilities during penetration tests.

Core Features & Use Cases

  • Multi-Source Version Extraction: Pulls plugin versions from readme.txt, PHP headers, asset paths, and REST API namespaces to avoid false positives from outdated readme files.
  • Cross-Database CVE Matching: Queries WPScan, Patchstack, and NVD databases to map extracted versions to known CVEs with severity ratings and fixed version data.
  • PoC Generation & False Positive Elimination: Provides exploitation proof-of-concept commands for confirmed CVEs and includes validation checks to confirm endpoints are reachable and versions are accurate before testing.
  • Use Case: A red teamer testing 15 WordPress targets can use this skill to quickly identify which plugins have unpatched critical CVEs, cutting hours of manual research into a repeatable workflow that has already found 14 confirmed exploitable CVEs across 58 real-world company targets.

Quick Start

Use the wp-plugin-cve-hunt skill to identify all exploitable CVEs for the WordPress plugins detected on your list of target domains, including version verification and PoC generation for confirmed vulnerabilities.

Frequently Asked Questions about wp-plugin-cve-hunt

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

FAQPage Schema
How do I find exploitable WordPress plugin CVEs across multiple target domains?

To find exploitable WordPress plugin CVEs across multiple targets, systematically extract plugin versions from readme.txt, PHP headers, and REST APIs, then cross-reference them against WPScan, NVD, and Patchstack databases.

How does multi-source version extraction eliminate false positives in WordPress vulnerability scanning?

Multi-source version extraction eliminates false positives in WordPress vulnerability scanning by pulling version data from readme.txt, PHP headers, asset paths, and REST API namespaces, avoiding reliance on outdated readme files.

What is the best way to automate WordPress plugin vulnerability checks for red team reconnaissance?

The best way to automate WordPress plugin vulnerability checks for red team reconnaissance is systematically detecting versions across target lists and cross-referencing them against public vulnerability databases to generate confirmed PoCs.

Does this WordPress CVE matching approach provide proof-of-concept commands for confirmed vulnerabilities?

Yes, the approach provides exploitation proof-of-concept commands for confirmed CVEs and includes validation checks to confirm endpoints are reachable and versions are accurate before testing.

Can I use wp-plugin-cve-hunt for mass target lists during penetration testing?

Yes, wp-plugin-cve-hunt is designed for penetration testing and red team workflows involving mass WordPress target lists, cutting hours of manual research into a repeatable workflow for confirmed exploitable CVEs.