Free tool
Check your site for the PHP2Shell flaws, outdated WordPress, SSL problems and missing security headers. It takes about ten seconds, and every finding comes with a plain-English fix.
Version data checked 6 November 2026 against official PHP and WordPress releases
Happening now
PHP2Shell is being actively exploited. It is fixed in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 (released 21 October 2026). Separately, WordPress 7.1.4 (28 October 2026) fixes an upgrade-process flaw that can lead to remote code execution. If your site runs PHP or WordPress, check it below.
What we check
The same things an attacker can see in a few seconds, so you can fix them first.
Sources: PHP security advisory, 21 October 2026, PHP supported versions, WordPress 7.1.4 security release, 28 October 2026.
Read more
Stay patched
Our managed service keeps PHP, WordPress, plugins and certificates up to date, monitors your site around the clock and tests backups by restoring them. When the next PHP2Shell arrives, it is already handled.
See managed servicesFAQ
The PHP project released fixes on 21 October 2026 in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Anything older on those branches is affected. PHP 8.1 and earlier no longer receive updates from the PHP project, so treat them as vulnerable unless your host has backported the fix.
WordPress 7.1.4, released on 28 October 2026, fixes a weakness in the upgrade process that can lead to remote code execution. WordPress says the fix is being backported to older branches, so the newest security release of your branch may also include it.
Yes. It loads your public homepage once, the same way a browser does, and reads the response headers, certificate and page source. It never logs in, never submits forms and never tries to exploit anything.
Not necessarily. Hiding the version is good practice, but the only way to be sure is to check the version on the server itself, or ask your hosting provider to confirm it is on a fixed release.
Update PHP and WordPress first, because those flaws are being actively exploited. Then renew or fix your SSL certificate and add the missing security headers. If you would like help, send us the report and an engineer will tell you what to fix first.