phpwarden vs. WPScan CLI
WPScan is the well-known black-box WordPress scanner, backed by the WPScan vulnerability database (owned by Automattic since 2021). phpwarden scans WordPress from disk plus the PHP engine and Composer, ranked by exploitation. How they differ, as of November 2026.
Short version: WPScan looks at a WordPress site from the outside, the way an
attacker would: it fingerprints the version, enumerates plugins, themes and user names, and finds exposed backups.
That makes it the stronger tool for a penetration test of a site you do not have files for. phpwarden works from the
files on the server (or in CI), so it sees every installed plugin exactly, and it also covers the PHP engine,
Composer and your own code, ranked by CISA KEV, then EPSS. Agencies with server access often run both.
Feature comparison
| WPScan CLI | phpwarden | |
|---|---|---|
| Scans a WordPress site from outside (black box) | ✓ Yes | read-only probe; active checks only after ownership proof |
| Enumerates user names | ✓ Yes | ✗ No |
| Finds exposed backups and config backups | ✓ Yes | ✗ not enumerated; probe reports a short list of exposures |
| Plugin / theme detection | ✓ from outside; can miss what is not exposed | ✓ from disk: exact versions |
| Vulnerability database | ✓ WPScan database, own research | open data: about 12,300 WordPress advisories |
| Composer dependency CVEs | ✗ No | ✓ Yes |
| PHP engine version CVEs | ✗ No | ✓ Yes |
| Scans your own plugin or theme code | ✗ No | ✓ 89 rules, WordPress-aware |
| Exploitation ranking (CISA KEV, then EPSS, then CVSS) | ✗ No | ✓ Yes |
| File integrity vs wordpress.org checksums | ✗ No | ✓ phpwarden integrity |
| Runtime blocking | ✗ No | ✓ shield, log-only until promoted |
| Vulnerability data without an account | ✗ API token; free plan (non-commercial) has a daily request limit | ✓ bundled feed, free weekly update |
| License | WPScan Public Source License; a commercial licence is needed to resell it or run it as a service | ✓ Apache-2.0 |
| Runtime | Ruby gem, Docker | Python 3.8+, zero deps; Docker; Composer |
| Cost | free plan and paid API plans; check their site | Free; Pro $39/mo; Team $149/mo |
Where WPScan is stronger
- Outside-in enumeration. WPScan can enumerate users, plugins, themes and backup folders on a site you only have a URL for. phpwarden's probe is deliberately limited: read-only, GET and HEAD only, and homepage-only until you prove you own the site.
- A dedicated WordPress database. WPScan maintains its own WordPress vulnerability database, owned by Automattic since 2021, with its own research. phpwarden builds from open data (OSV, NVD, CISA KEV, FIRST EPSS and others).
- Pentest tooling. WPScan's license explicitly covers penetration testers and security distributions, and it is built for testing sites you are authorised to test. phpwarden is built for sites you own or host.
Where phpwarden differs
- From disk, exact. Scanning the files means a plugin that hides its readme is still found at its exact version, and it works in CI before deploy.
- Whole stack. The PHP engine and Composer dependencies, not only WordPress, plus your own code and Trivy
results in one ranked list (
phpwarden assess). - Exploitation first. Of about 19,500 distinct vulnerabilities in the feed, 54 are on CISA KEV, and they sit at the top of every report.
- Signed-in check, safely. Since 2.5.0, on a verified site, the probe can log in with a low-privilege test account (one same-origin login, then GET and HEAD only) to read versions only visible when logged in. Credentials are stored encrypted and never printed.
- Agency workflow. Team adds client reports with your logo and free view-only client logins.
When to use WPScan instead
For a black-box assessment of a WordPress site you have no file access to, or when you need user enumeration and backup discovery, use WPScan. For sites you host or build, phpwarden from disk gives exact versions and the rest of the PHP stack.
Try phpwarden on your project
Zero dependencies, offline, Apache-2.0. Ranks findings by CISA KEV → EPSS → CVSS.
composer require --dev phpwarden/phpwarden # PHP projects → vendor/bin/phpwarden
vendor/bin/phpwarden deps composer.lock # Composer
vendor/bin/phpwarden scan # PHP engine on this host
vendor/bin/phpwarden wordpress /var/www/html # WordPress core, plugins, themes
No Composer? pipx install phpwarden or the single-file phpwarden.pyz. In CI: oroma-alfred/phpwarden-action@v1.
About this comparison
- wpscanteam/wpscan (GitHub README: enumeration options, API token, license)
- WPScan API plans
- WPScan joins Automattic (2021)
- phpwarden pricing: Free ($0: CLI, bundled feed, free weekly feed updates, one dashboard project); Pro $39/month (maintained feed rebuilt twice a day, up to 25 projects, weekly live check of each verified site, alerts); Team $149/month (unlimited projects, client reports with your logo, view-only client logins, 5 staff seats, partner API).