The best WordPress vulnerability scanners in 2026

Comparing the tools that scan WordPress for vulnerabilities and malware (Wordfence CLI, Patchstack, phpwarden and WPScan) and what each is best at.

WordPress security tooling splits into three jobs: finding known-vulnerable core/plugins/themes, detecting injected malware, and blocking exploitation at runtime. No tool does all three best. Here's the honest breakdown (November 2026); we make phpwarden, so weigh our own entry accordingly.

phpwarden

Best for: exploitation-ranked WordPress exposure, alongside Composer and the PHP engine

Scans WordPress core, plugins and themes off disk (about 12,300 WordPress advisories in its feed) and ranks by CISA KEV, then EPSS, then CVSS, so the actively-exploited plugin bug surfaces first. Also covers Composer and the PHP engine, useful because WordPress sites run on a PHP version and often ship Composer packages too. Its live check looks at a site you manage from outside (exposed .env and .git files, debug pages, the versions it gives away), only after the site proves it is yours, and re-checks show what is fixed and verified. A file integrity check catches tampered core and plugin files, a whole-program code scan (89 rules) checks the plugin or theme code you wrote, and it can generate ModSecurity or nginx rules with a log-only trial first. Free CLI, offline, Apache-2.0. No malware signatures, no managed virtual patching.

Wordfence CLI

Best for: malware cleanup, while an existing licence lasts

Open-source Python CLI with known-vulnerability scanning and malware/backdoor detection. Being wound down: no new licences are available; Free licences ended 2026-10-14. The Wordfence plugin is unaffected. phpwarden vs Wordfence CLI, with a migration table →

Patchstack

Best for: managed protection + virtual patching

Managed service with strong plugin vulnerability intelligence and virtual patching that mitigates a disclosed bug at runtime before you update. Paid. Ideal for agencies and hosts wanting hands-off protection. phpwarden vs Patchstack →

WPScan

Best for: black-box scanning of a live WordPress URL

A long-standing scanner (and WordPress vulnerability database) that enumerates a running WordPress site remotely (version, plugins, users) and matches against its database. Great for assessing a site you only have the URL for, rather than filesystem access. Uses an API token (free tier with a daily quota). Different approach from the filesystem scanners above.

How to choose

If you want to…Start with
Rank known WP vulns by real exploitation, + Composer/PHP enginephpwarden
Check sites you manage from outside and see which fixes are verified on re-checkphpwarden (live check)
Detect malware/backdoors in the filesWordfence plugin, or Wordfence CLI while a licence lasts
Managed protection with virtual patchingPatchstack
Scan a live site you only have the URL forWPScan

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

Or pipx install phpwarden, or 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: