phpwarden vs. Wordfence CLI

Wordfence CLI, the command-line scanner for WordPress malware and vulnerabilities, is being wound down (no new licences are available; Free licences ended 2026-10-14). phpwarden scans WordPress plus the PHP engine and Composer, ranked by CISA KEV, then EPSS. What it replaces and what it does not.

Update, November 2026: Wordfence is winding the CLI down. Its GitHub README says no new Free or Premium licences are available, Free licences stopped working on 2026-10-14, and existing Premium licences will not be renewed. The code stays on GitHub under GPLv3, but its malware signatures and vulnerability data need a licence. If you relied on its vuln-scan, phpwarden replaces it directly. For malware-scan, phpwarden has a file integrity check that catches tampered and injected files, but it is not a signature scanner. The migration table below maps each command.
Short version: Wordfence CLI was excellent for WordPress specifically, and it did one thing phpwarden does not: malware scanning (detecting injected/backdoor files). phpwarden covers WordPress vulnerabilities and the PHP engine and Composer dependencies in one tool, ranked by real-world exploitation. If you only run WordPress and want malware detection, the Wordfence plugin, or Wordfence CLI while an existing Premium licence lasts, makes sense. If you want one scanner across your whole PHP stack ranked by what's actually exploited, phpwarden.

Feature comparison

Wordfence CLIphpwarden
WordPress core / plugin / theme CVEs✓ Yes✓ Yes
Malware signatures (known malware families)✓ Yes✗ No
File integrity vs wordpress.org checksumscheck their docs✓ core + plugins
Injected files and common backdoor code✓ Yes✓ heuristic
Composer dependency CVEs✗ No✓ Yes
PHP engine version CVEs (per branch/SAPI)✗ No✓ Yes
Exploitation ranking (CISA KEV + EPSS)✗ own severity✓ Yes
Runtime protection (PHP-FPM guard)✗ No✓ paid: dry-run on Pro, enforce on Team
Scans your own PHP code (whole program, framework-aware)✗ No✓ 89 rules, cross-file, WordPress-aware
Live check of the running site from outside✗ No✓ read-only, ownership-verified
Signed-in live check (versions only visible when logged in)✗ No✓ since 2.5.0: test account or cookie, GET/HEAD only
Imports Trivy results (npm, OS packages, IaC, secrets)✗ No✓ phpwarden trivy-import, assess --trivy
Editor integration✗ No✓ VS Code extension (Marketplace); PhpStorm plugin from disk
Client reports for agencies✗ No✓ client-ready report free; your logo on Team
One combined, ranked verdict (versions, code, live site, logs)✗ No✓ phpwarden assess
WAF rules you run yourself✗ No✓ ModSecurity / nginx; log-only trial
Blocks exploits of the vulnerabilities installed, inside PHP✗ No✓ shield: per-site rules, log-only first
Vulnerability data freshnessneeds a licencebundled; free weekly update; twice daily on Pro; exploited CVEs within 24 hours
Runs offline / free vuln scanning✗ needs a licence; Free licences ended 2026-10-14✓ Yes
Open source✓ GPLv3✓ Apache-2.0 engine
Language / runtimePython 3.8+, libpcrePython 3.8+, zero deps
New licences available✗ closed Oct 2026✓ Yes
JSON / SARIF output✗ CSV/TSV and line-delimited only✓ Yes
CostNo longer soldFree; Pro $39/mo; Team $149/mo

Replacing Wordfence CLI, command by command

Wordfence CLIphpwardenWhat you keep, what you lose
wordfence vuln-scan /var/www/sitephpwarden wordpress /var/www/siteSame job. You gain exploitation ranking, JSON and SARIF output and a non-zero exit code on findings.
wordfence malware-scan /var/www/sitephpwarden integrity /var/www/siteFinds modified core and plugin files, files that do not belong, PHP in uploads and common backdoor code. No malware signatures: malware inside a premium plugin or a theme is not covered, and the report lists what it could not verify.
wordfence remediatenoneReinstall the flagged component: wp core download --force --version=X, or wp plugin install SLUG --force --version=Y.
wordfence db-scannonephpwarden does not scan the database.
cron + email output--json, exit codes, --report-toPipe JSON to your own tooling, or send results to the dashboard for a fleet view and alerts.

Scanning every site on a server:

for d in /var/www/*/public_html; do
  phpwarden wordpress "$d" --json > "/var/log/phpwarden/$(basename "$(dirname "$d")").json"
  phpwarden integrity "$d" || echo "TAMPERED: $d"
done

If malware signatures are a hard requirement, keep a signature scanner alongside: the Wordfence plugin on each site, or a server-level scanner such as Imunify360 or ClamAV with PHP malware rules.

What Wordfence CLI did well

Wordfence CLI is an open-source (GPLv3), high-performance Python scanner from the Wordfence team. Its vuln-scan checked a WordPress tree against the Wordfence Intelligence vulnerability database; its malware-scan detected malicious PHP files using Wordfence malware signatures. For a WordPress operator who needs to find injected malware, that malware capability is something phpwarden does not offer at all.

Where phpwarden differs

When to keep Wordfence CLI for now

If you hold a Premium CLI licence that is still in term, its signature-based malware scan remains the stronger tool for cleaning a site that is already compromised. Plan the move before the licence ends: phpwarden covers the vulnerability scan and tamper detection, across WordPress and Composer and the PHP engine, ranked by exploitation.

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: