About phpwarden
A PHP security tool that would rather tell you less and be right than tell you more and be wrong.
Who builds it
Oroma Alfred
Independent developer, security researcher and the maintainer of phpwarden.
I do bug bounty work, run my own servers, and build small tools I'd want to use myself, including offline AI that runs on your own machine. phpwarden came out of that: I wanted a scanner that told me what attackers are actually using.
phpwarden is built and run by one person, in the open. There is no sales team between you and the person who wrote the code — whichever address on this page you write to, I'm the one who reads it.
Why it exists
Every PHP vulnerability scanner I tried did one of two things. It sorted findings by CVSS, so a 9.8 that nobody exploits sat above a 7.5 that was in CISA's Known Exploited Vulnerabilities catalog. Or it told me "you're on PHP 8.1, upgrade" when PHP backports fixes per branch and the only question that matters is whether my 8.1.x has the fix. Both produce a wall of red that teams learn to ignore — which is worse than no scanner.
So phpwarden ranks by what is actually being exploited (KEV first, then EPSS, then CVSS), checks the PHP engine per branch and per SAPI, scans Composer dependencies with a reachability check, and covers WordPress core, plugins and themes — in one zero-dependency tool that runs offline. The numbers behind that design are public: of about 19,500 PHP vulnerabilities in the feed, 54 are known to be exploited (as of 14 November 2026; monthly report).
What it's built on
claim=REFUSED otherwise). Daemon up is not the same as protected.What it is and isn't
- It is an exposure scanner for the PHP engine, Composer and WordPress, plus a WordPress file integrity check (core and plugins against wordpress.org checksums, PHP in uploads, known backdoor patterns), a PHP-FPM runtime guard for memory-corruption exploitation, a whole-program security analyser for your own PHP code, a read-only live check of a site from outside, and a shield inside PHP that blocks exploits of the vulnerabilities a site has.
- It isn't a signature-based malware scanner, a WAF, or a virtual-patching service — I say which tools to use for those.
Reach a person
Questions, bugs, feed corrections, or you manage a lot of PHP sites and want to talk: [email protected] — despite the name, that's my inbox, not a sales team. Security issues: see the security policy. Agencies and hosts: the design partner program is open.
To hear when a PHP, Composer or WordPress vulnerability starts being exploited: follow @[email protected] on Mastodon, or use the feed or weekly email.
GitHub PyPI Packagist GitHub Action Docker Hub Homebrew Mastodon Changelog