phpwarden vs. Patchstack
Patchstack is a managed WordPress security service with a vulnerability database and virtual patching. phpwarden is a free, offline CLI scanner covering WordPress, Composer and the PHP engine, ranked by exploitation. Different tools for different jobs.
Feature comparison
| Patchstack | phpwarden | |
|---|---|---|
| WordPress vulnerability detection | ✓ Yes | ✓ Yes |
| Managed virtual patching | ✓ Yes | ✗ No |
| Composer dependency CVEs | ✗ No | ✓ Yes |
| PHP engine version CVEs | ✗ No | ✓ Yes |
| Exploitation ranking (CISA KEV + EPSS) | own intel | ✓ Yes |
| WAF rules you run yourself | ✗ managed virtual patches | ✓ ModSecurity / nginx; log-only trial |
| Blocks exploits of the vulnerabilities installed, inside PHP | virtual patches for WordPress plugins (managed); check their docs | ✓ shield: per-site rules you run, log-only first |
| Live check of the running site from outside | check their docs | ✓ read-only, ownership-verified |
| Scans your own PHP code | ✗ No | ✓ Yes |
| One combined, ranked verdict (versions, code, live site, logs) | ✗ No | ✓ phpwarden assess |
| SARIF output for code-scanning tabs | check their docs | ✓ Yes |
| Vulnerability data freshness | own research, often early for plugins | bundled; free weekly update; twice daily on Pro; exploited CVEs within 24 hours |
| Runs offline / self-hosted CLI | ✗ managed service | ✓ Yes |
| Open source | ✗ No | ✓ Apache-2.0 engine |
| Delivery | WP plugin + cloud | CLI / CI / daemon |
| Cost | Paid plans (free tier for the DB); check their site | Free; paid feed optional |
What Patchstack does well
Patchstack maintains a large, well-regarded WordPress vulnerability database and runs a managed VDP (vulnerability disclosure program), so it often has plugin advisories early. Its headline capability is virtual patching: when a plugin vulnerability is disclosed, Patchstack can deploy a mitigation rule that blocks exploitation at runtime even before the plugin author ships a fix, which is valuable for sites that can't update instantly. It serves developers, agencies and hosts as a managed service.
Where phpwarden differs
- Scanner first; blocking is self-run. phpwarden tells you what you're exposed to and how urgent it is.
phpwarden shieldcan block exploits of that site's own exploited vulnerabilities inside PHP, logging only until you promote it, but nothing is managed for you and there is no edge firewall. It also has the PHP-FPM guard daemon (memory-corruption exploitation, on the paid plans: dry-run on Pro, enforce on Team), which is a different mechanism from Patchstack's WordPress virtual patches. It can also generate ModSecurity or nginx rules you run yourself, with a log-only trial first. - Beyond WordPress. phpwarden also covers Composer dependencies and the PHP engine version (the parts of a PHP app that live outside WordPress), plus your own PHP code and a read-only check of the live site from outside.
- Free, offline, open. phpwarden runs on your machine with no account and ships its feed; the engine is Apache-2.0. Patchstack is a commercial managed service.
- Exploitation ranking in the open. Every CVE phpwarden knows has a public page with its KEV/EPSS standing. The maintained feed is rebuilt twice a day and commits to carrying newly exploited vulnerabilities within 24 hours (commitment); Patchstack's own research often has plugin advisories earlier than public sources.
- Shield, run by you.
phpwarden shieldwrites rules only for the exploited vulnerabilities installed on a site and enforces them inside PHP; it logs until you promote a rule. Patchstack's virtual patching is a managed service with its own research; phpwarden's shield is a file you run and audit (how it works). - One verdict.
phpwarden assessranks installed versions, your own code, the live site and your access log together, with the reason for each item.
When to use Patchstack instead
If you run WordPress sites for clients and want hands-off, managed protection (early plugin intelligence plus virtual patching that buys time between disclosure and update), Patchstack does something phpwarden doesn't. phpwarden is for teams that want to audit their PHP stack themselves, free and offline, and prioritise fixes by real exploitation. The two can coexist: phpwarden in CI/on the server for exposure, Patchstack for managed runtime WordPress mitigation.
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
- Patchstack vulnerability database
- Patchstack pricing and plan details: see patchstack.com (figures change).
- phpwarden advisory feed