Cyber Services / All lessons / CEH — Ethical Hacking / WPProbe Security Scanner

WPProbe Security Scanner

Module 19 of 130 · 11 min read · Free to read

MODULES ↓ Command blocks have a COPY button

⚠️ AUTHORIZED SECURITY TESTING ONLY

WPProbe is a professional security scanning tool designed for authorized penetration testing and vulnerability assessment.

  • ✅ Use ONLY on WordPress sites you own or have explicit written permission to test
  • ✅ Comply with responsible disclosure practices and local cybersecurity laws
  • ✅ Document all testing activities with timestamps and authorization records
  • ❌ NEVER scan websites, plugins, or themes without proper authorization
  • ❌ Unauthorized scanning may violate computer fraud laws and terms of service

"Because why scan blind when WordPress exposes itself?"

Fast WordPress Plugin & Theme Scanner • REST API Enumeration • CVE Mapping • 5000+ Plugins

👨‍💻 Documentation by: Mubasher Mubeen | Security Trainer | CEH v13
🎯

Case Study: WordPress Vulnerability Assessment Workflow

Scenario: A security consultant is engaged to assess a client's WordPress installation (https://client-site.com). The client reports suspicious activity and wants to identify vulnerable plugins before a potential breach.

🔍 Initial Reconnaissance Findings:
  • WordPress version exposed in HTML meta tags (6.4.2)
  • REST API endpoint accessible at /wp-json/
  • Multiple plugins detected via ?rest_route=/ enumeration
  • Theme "Astra" identified with outdated version (3.8.1)
  • Wordfence plugin present but not properly configured
✅ WPProbe Assessment Procedure:
// Step 1: Update vulnerability database (uses pre-built CI database) wpprobe update-db [+] Database updated: 5,247 plugins, 1,892 themes, 12,453 CVEs // Step 2: Run stealthy scan against target wpprobe scan -u https://client-site.com --mode stealthy -o results.json [+] Target: https://client-site.com [+] WordPress version: 6.4.2 [+] Plugins found: 12 (3 vulnerable) [+] Themes found: 1 (1 vulnerable) // Step 3: Search for specific CVE details wpprobe search --plugin woocommerce --details Plugin: woocommerce CVE-2024-34567: SQL Injection (CVSS: 9.8) - Versions < 8.5.2 // Step 4: Generate professional report wpprobe scan -u https://client-site.com -o report.pdf --format pdf [+] Report saved: report.pdf
💡 Pro Tip: WPProbe v0.10.16+ uses a pre-built database updated every 2 hours via CI, so no Wordfence API key is required for basic scanning. Use --api-key only if you need real-time Wordfence data.

🔧 Common WPProbe Issues & Fixes

Issue Diagnosis Solution
update-db fails (pre-v0.10.16) Wordfence API v2 deprecated March 2026 Upgrade: go install github.com/Chocapikk/wpprobe@latest
No plugins detected REST API disabled or filtered by WAF Try --mode bruteforce or check /wp-json/ manually
Rate limited by target Too many requests in short time Add --rate-limit 5 or increase delay between requests
False positive plugins 403 responses misinterpreted Use --no-check-version or verify manually
Database not found First run without internet Run wpprobe update-db with network access first
📋 WPProbe Quick Reference Card
// INSTALLATION go install github.com/Chocapikk/wpprobe@latest wpprobe update-db // BASIC SCAN wpprobe scan -u https://target.com wpprobe scan -u https://target.com --mode hybrid -t 10 // OUTPUT FORMATS wpprobe scan -u https://target.com -o results.json wpprobe scan -u https://target.com -o results.csv wpprobe scan -u https://target.com -o report.txt // DATABASE QUERIES wpprobe search --plugin woocommerce wpprobe search --cve CVE-2024-1234 --details wpprobe search --severity critical --auth Unauth wpprobe list // ADVANCED OPTIONS wpprobe scan -u https://target.com \ --header "User-Agent: CustomBot/1.0" \ --proxy http://127.0.0.1:8080 \ --rate-limit 3 \ --no-check-version \ --timeout 30 // SELF-UPDATE wpprobe update
📊

WPProbe Overview & Capabilities

🎯 Key Features

  • 🔍 REST API Enumeration: Detect 5000+ plugins via exposed WordPress REST endpoints without brute-forcing
  • 🎨 Theme Discovery: Identify active themes by parsing wp-content/themes/ references from HTML
  • 🦠 CVE Mapping: Correlate detected plugins/themes with known vulnerabilities from Wordfence & WPScan databases
  • ⚡ High Performance: Concurrent scanning with configurable threading and rate limiting
  • 📤 Flexible Output: Export results to JSON, CSV, TXT, or PDF formats for reporting
  • 🔄 Auto-Update: Self-updating binary and vulnerability database via CI/CD pipeline
5,247+
Detectable Plugins (Stealthy)
10,000+
Plugins (Brute-force Mode)
12,453+
Mapped CVEs
<30s
Avg Scan Time (Stealthy)
🐧 Kali Linux
Pre-installed in kali-rolling
🔧 Go 1.22+
For building from source
🐳 Docker
Containerized execution
🔐 Authorization
Written permission required
1
Install
2
Update DB
3
Scan
4
Report
⚙️

Installation Methods

Multiple Installation Options

📦 Choose Your Installation Method

🐧

Kali Linux

Pre-packaged in kali-rolling repository

sudo apt install wpprobe
🔧

Go Install

Requires Go 1.22 or newer

go install github.com/Chocapikk/wpprobe@latest
🐳

Docker

Containerized, no local install

docker run -it --rm wpprobe scan -u https://target.com
❄️

Nix

Nix package manager support

nix-shell -p wpprobe

🔧 From Source (Advanced)

  1. Clone and build:
    // Clone repository git clone https://github.com/Chocapikk/wpprobe // Navigate to directory cd wpprobe // Build binary go build -o wpprobe // Verify installation ./wpprobe version WPProbe v0.10.16 (linux/amd64)
  2. Optional: Install to PATH:
    // Move binary to system PATH sudo cp ./wpprobe /usr/local/bin/ sudo chmod +x /usr/local/bin/wpprobe // Verify global access wpprobe --help
💡 Docker with File Mounting:
To save results to your host machine when using Docker:
docker run -it --rm \ -v $(pwd):/results \ wpprobe \ scan -u https://target.com -o /results/output.json
🎚️

Scanning Modes Comparison

Choose the Right Mode

🔍 Understanding WPProbe Scanning Modes

WPProbe offers three scanning modes to balance stealth, speed, and coverage based on your engagement requirements.

Mode Method Stealth Level Coverage Best For
stealthy Default REST API endpoint matching + HTML theme discovery 🟢 High 5,000+ plugins + themes Initial recon, WAF evasion, low-noise assessments
bruteforce Advanced Direct directory checks via GET requests 🔴 Low 10,000+ plugins Comprehensive audits, internal assessments, no WAF concerns
hybrid Balanced Stealthy first, then brute-force remaining 🟡 Medium Maximum coverage Full penetration tests, red team engagements

⚙️ Mode Usage Examples

  1. Stealthy Mode (Default):
    // Basic stealthy scan wpprobe scan -u https://target.com // With custom headers and rate limiting wpprobe scan -u https://target.com \ --mode stealthy \ --header "User-Agent: Mozilla/5.0" \ --rate-limit 2 \ -o stealth_results.json
  2. Brute-force Mode:
    // Aggressive plugin enumeration wpprobe scan -u https://target.com \ --mode bruteforce \ -t 20 \ --rate-limit 10 \ -o brute_results.csv // With custom wordlist (if supported) wpprobe scan -u https://target.com \ --mode bruteforce \ --wordlist /path/to/custom_plugins.txt
  3. Hybrid Mode:
    // Maximum coverage with progressive approach wpprobe scan -u https://target.com \ --mode hybrid \ -t 15 \ --rate-limit 5 \ --timeout 30 \ -o hybrid_report.json
🔒 Mode Selection Guidelines:
  • Stealthy: Use for external assessments, bug bounty programs, or when WAF/IDS is present
  • Brute-force: Only use on systems you own or have explicit authorization for aggressive scanning
  • Hybrid: Recommended for comprehensive penetration tests with proper authorization
  • Always start with --rate-limit to avoid triggering rate limiting or blocking
🚀

Usage Examples & Output Formats

Hands-on Examples

🎯 Basic Scanning Commands

  1. Single Target Scan:
    // Quick scan with default settings wpprobe scan -u https://example.com // Expected output format [+] Target: https://example.com [+] WordPress version: 6.4.2 [+] Plugins found: 8 ├── contact-form-7 (5.8.4) - ✓ No known vulnerabilities ├── woocommerce (8.2.1) - ⚠️ CVE-2024-34567 (CVSS: 9.8) ├── yoast-seo (21.5) - ✓ No known vulnerabilities [+] Themes found: 1 └── astra (3.8.1) - ⚠️ CVE-2024-12345 (CVSS: 7.5) [+] Scan completed in 28.4s
  2. Multiple Targets with Threading:
    // Create targets file cat > targets.txt << 'EOF' https://site1.com https://site2.com https://site3.com EOF // Scan multiple targets concurrently wpprobe scan -f targets.txt -t 20 -o batch_results.json [+] Scanning 3 targets with 20 threads [+] [1/3] https://site1.com - Completed [+] [2/3] https://site2.com - Completed [+] [3/3] https://site3.com - Completed [+] All scans completed. Results saved to batch_results.json
  3. Advanced Options:
    // Custom headers, proxy, and rate limiting wpprobe scan -u https://target.com \ --header "User-Agent: SecurityBot/1.0" \ --header "Authorization: Bearer token123" \ --proxy http://127.0.0.1:8080 \ --rate-limit 3 \ --timeout 30 \ --no-check-version \ -o advanced_scan.json // Skip version checking for faster scans (less accurate) wpprobe scan -u https://target.com --no-check-version

📤 Output Format Examples

JSON Output

Structured data for automation and parsing

{ "target": "https://example.com", "wordpress_version": "6.4.2", "plugins": [ { "name": "woocommerce", "version": "8.2.1", "vulnerable": true, "cves": ["CVE-2024-34567"] } ], "themes": [...], "scan_time": "28.4s" }

CSV Output

Spreadsheet-compatible for reporting

target,plugin,version,vulnerable,cve,cvss example.com,woocommerce,8.2.1,true,CVE-2024-34567,9.8 example.com,astra,3.8.1,true,CVE-2024-12345,7.5

Text Output

Human-readable for quick review

Target: https://example.com WordPress: 6.4.2 Plugins: ✓ contact-form-7 (5.8.4) ⚠️ woocommerce (8.2.1) - CVE-2024-34567 (CVSS: 9.8) Themes: ⚠️ astra (3.8.1) - CVE-2024-12345 (CVSS: 7.5)

🗄️ Vulnerability Database Management

  1. Update Database (Default - Pre-built CI):
    // Fetch pre-built database (no API key needed) wpprobe update-db [+] Downloading pre-built database from CI... [+] Database updated: 5,247 plugins, 1,892 themes, 12,453 CVEs [+] Last updated: 2026-05-09 14:30 UTC
  2. Update with Wordfence API Key (Optional):
    // Get free API key from wordfence.com → Account → Integrations // Method 1: Command line flag wpprobe update-db --api-key your_wordfence_key_here // Method 2: Environment variable export WORDFENCE_API_KEY=your_wordfence_key_here wpprobe update-db
  3. Search Vulnerability Database:
    // Search by CVE ID wpprobe search --cve CVE-2024-1234 // Search by plugin name wpprobe search --plugin woocommerce // Filter by severity and authentication type wpprobe search --severity critical --auth Unauth // Search by vulnerability title with full details wpprobe search --title "SQL Injection" --details Plugin: example-plugin CVE: CVE-2024-5678 CVSS: 9.8 (Critical) Type: SQL Injection Auth: Unauthenticated Affected: <= 2.3.1 Description: SQL injection in search parameter... POC: https://example.com/poc // List database statistics wpprobe list Plugins: 5,247 | Themes: 1,892 | CVEs: 12,453 Last update: 2026-05-09 14:30 UTC
💡 Environment Variables Reference:
Variable Description Example
WORDFENCE_API_KEY Wordfence API key for real-time DB updates export WORDFENCE_API_KEY=abc123
WPSCAN_API_TOKEN WPScan Enterprise token (paid) export WPSCAN_API_TOKEN=xyz789
HTTP_PROXY HTTP proxy configuration export HTTP_PROXY=http://proxy:8080
NO_PROXY Proxy bypass rules export NO_PROXY=localhost,127.0.0.1
⚙️

How WPProbe Works: Technical Deep Dive

🔍 Stealthy Mode Architecture

REST API Enumeration

Queries ?rest_route=/ endpoints and matches discovered paths against a precompiled signature database of known plugin REST routes. Minimal requests, maximum detection.

HTML Theme Discovery

Parses page HTML for wp-content/themes/ references, extracts theme names, then fetches style.css to determine version without brute-forcing.

Signature Matching

Uses a curated database of 5,000+ plugin signatures (REST routes, JS/CSS paths, meta tags) for accurate identification without directory brute-forcing.

Version Correlation

Extracts version from plugin headers, readme.txt, or style.css, then correlates with CVE database using semantic version range matching.

⚔️ Brute-force Mode Methodology

  1. Directory Probing:
    // Sends GET requests to common plugin paths // Example: /wp-content/plugins/contact-form-7/ // Response interpretation: // 403 Forbidden → Plugin EXISTS (directory listing blocked) // 404 Not Found → Plugin likely NOT installed // 200 OK → Validate by checking for readme.txt to avoid false positives
  2. False Positive Mitigation:
    // Some WordPress configs return 200 for all paths // WPProbe validates by checking for plugin-specific files: // If 200 response received: // 1. Check for /readme.txt in plugin directory // 2. Parse readme.txt for "Plugin Name" header // 3. Confirm match before reporting plugin as found

🔄 Hybrid Mode Workflow

🖼️ Hybrid Mode Process Flow
1️⃣ Stealthy scan (REST API + HTML) → Detect easy plugins
2️⃣ Filter detected plugins from brute-force list
3️⃣ Brute-force remaining plugins only
4️⃣ Merge results, deduplicate, correlate with CVEs
5️⃣ Output consolidated report
💡 Performance Optimization Tips:
✓ Use --rate-limit to avoid triggering WAF rate limiting
✓ Start with stealthy mode before escalating to bruteforce
✓ Use -t (threads) wisely: 10-20 for most targets, lower for fragile sites
✓ Cache results with -o to avoid re-scanning during report generation
⚠️

Limitations & Professional Best Practices

🔍 Known Limitations by Mode

Mode Limitation Mitigation Strategy
Stealthy Plugins without REST API endpoints may be missed Follow up with --mode hybrid for comprehensive coverage
Stealthy Disabled/hidden plugins not detected Combine with manual review of wp-config.php if authorized
Stealthy Themes loaded dynamically may be missed Check multiple pages (home, posts, archive) for theme references
Brute-force High request volume may trigger WAF/IDS Use --rate-limit 1-3 and monitor for blocks
Brute-force Limited by wordlist coverage Supplement with custom wordlists for niche plugins
Brute-force Does not brute-force themes by design Theme detection always uses HTML parsing regardless of mode
Hybrid Slower than pure stealthy due to brute-force phase Use for final comprehensive scan after initial stealthy recon

🛡️ Professional Usage Guidelines

Authorization First

Always obtain written permission before scanning. Document scope, targets, and methods in your engagement letter.

Start Low, Scale Up

Begin with stealthy mode and low thread counts. Escalate only if authorized and necessary.

Respect Rate Limits

Use --rate-limit to avoid overwhelming targets. Monitor for HTTP 429 responses and back off.

Document Everything

Log all commands, timestamps, and results. Preserve output files with cryptographic hashes for audit trails.

Responsible Disclosure

If you find vulnerabilities, follow responsible disclosure practices. Report to site owners before public disclosure.

Stay Updated

Run wpprobe update regularly. Vulnerability databases evolve; outdated tools miss new CVEs.

⚠️ Wordfence API Change Notice (March 2026):
Wordfence deprecated their v2 API on March 9, 2026. WPProbe versions prior to v0.10.16 have broken update-db functionality.
  • ✅ Fix: Update to v0.10.16+: go install github.com/Chocapikk/wpprobe@latest
  • ✅ Default behavior: Pre-built database from CI (updated every 2h) - no API key needed
  • ✅ Optional: Set WORDFENCE_API_KEY if you need real-time Wordfence data
🔄

Self-Update & Contributing

🔄 Keeping WPProbe Updated

  1. Self-Update Command:
    // Update WPProbe binary to latest release wpprobe update [+] Checking for updates... [+] New version available: v0.10.17 [+] Downloading update... [+] Update complete. Restart WPProbe to apply changes. // Verify update wpprobe version WPProbe v0.10.17 (linux/amd64)
  2. Manual Update (if self-update fails):
    // Reinstall via Go go install github.com/Chocapikk/wpprobe@latest // Or download release binary from GitHub wget https://github.com/Chocapikk/wpprobe/releases/latest/download/wpprobe_linux_amd64.tar.gz tar -xzf wpprobe_linux_amd64.tar.gz sudo mv wpprobe /usr/local/bin/

🤝 Contributing to WPProbe

Report Issues

Found a bug or false positive? Open an issue on GitHub with reproduction steps, target details (sanitized), and WPProbe version.

Submit Plugin Signatures

Help expand the stealthy detection database by submitting new plugin REST route signatures via pull request.

Improve Documentation

Clear docs help everyone. Submit PRs to improve examples, fix typos, or add usage scenarios.

Code Contributions

Want to add a feature? Fork the repo, create a feature branch, and submit a PR with tests and documentation.

💡 Contribution Quick Start:
// Fork and clone git clone https://github.com/YOUR_USERNAME/wpprobe cd wpprobe // Create feature branch git checkout -b feature/your-feature-name // Make changes, test locally go build -o wpprobe ./wpprobe scan -u https://test-target.local // Commit and push git add . git commit -m "feat: add new plugin signature for xyz-plugin" git push origin feature/your-feature-name // Submit PR via GitHub UI
Modules (130) ← CEH — Ethical Hacking