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 CLIphpwarden
Scans a WordPress site from outside (black box)✓ Yesread-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 researchopen 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
LicenseWPScan Public Source License; a commercial licence is needed to resell it or run it as a service✓ Apache-2.0
RuntimeRuby gem, DockerPython 3.8+, zero deps; Docker; Composer
Costfree plan and paid API plans; check their siteFree; Pro $39/mo; Team $149/mo

Where WPScan is stronger

Where phpwarden differs

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

Competitor details reflect each vendor's public documentation as of November 2026 and may have changed. Check their own sites for current pricing and features. phpwarden is our own tool, so we have a stake here; we've tried to state only verifiable facts and to say plainly when another tool is the better fit. Spotted an error? We'll correct it. Sources: