wordpress-plugin-hunt

Detect installed WordPress plugins and cross-reference versions against known CVEs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually identifying installed WordPress plugins and their associated CVEs is time-consuming and error-prone for security professionals conducting penetration tests or reconnaissance on WordPress targets.

Core Features & Use Cases

  • Multi-method plugin detection: Probes 40+ common plugin REST API namespaces, checks readme.txt for version data, and scans HTML/JS source for plugin fingerprints.
  • CVE cross-referencing: Automatically flags outdated plugin versions with known exploitable vulnerabilities including RCE, SQLi, and privilege escalation for high-risk plugins like Slider Revolution, Elementor, and Gravity Forms.
  • Use case: For a penetration test targeting a WordPress e-commerce site, use this skill to quickly identify outdated WooCommerce or LiteSpeed Cache instances with publicly available exploit PoCs.

Quick Start

Use the wordpress-plugin-hunt skill to scan the target WordPress site example.com for installed plugins and check if any have known exploitable CVEs.

Frequently Asked Questions about wordpress-plugin-hunt

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

FAQPage Schema
How do I find installed WordPress plugins and check them for known CVEs?

To find WordPress plugins and check for CVEs, you can use automated reconnaissance tools that probe REST API namespaces, parse readme.txt files for version data, and cross-reference discovered versions against a curated vulnerability database.

What is the best way to detect outdated WordPress plugins during a penetration test?

The best way to detect outdated WordPress plugins is by fingerprinting HTML and JavaScript source code for plugin traces, then querying readme.txt files to extract exact version numbers for vulnerability cross-referencing.

Can I identify exploitable vulnerabilities like RCE or SQLi in WordPress plugins automatically?

Yes, you can identify exploitable vulnerabilities like RCE, SQLi, and privilege escalation by scanning detected WordPress plugin versions against a database of known CVEs to flag confirmed vulnerable instances.

Does WordPress plugin scanning work on e-commerce sites using WooCommerce?

Yes, WordPress plugin scanning works on e-commerce sites by probing common REST API namespaces and source fingerprints to identify installed plugins like WooCommerce or LiteSpeed Cache and flag their associated CVEs.

What methods are used for WordPress plugin version detection?

WordPress plugin version detection uses three primary methods: probing 40+ common plugin REST API namespaces, parsing readme.txt files for version headers, and scanning HTML and JS source code for plugin fingerprints.

When do I need to scan WordPress REST API namespaces for vulnerability reconnaissance?

You need to scan WordPress REST API namespaces during offensive security reconnaissance when targeting WordPress installations to enumerate installed plugins like Elementor or Gravity Forms and uncover exploitable CVEs.