At riskPHP 8.1 and older; unpatched 8.2 to 8.5
Safe from8.2.35 · 8.3.36 · 8.4.27 · 8.5.12
How we lookOne ordinary page visit. Nothing intrusive.
Evidence
What to do
- Update PHP to 8.2.35, 8.3.36, 8.4.27 or 8.5.12 or later. If PHP comes from your Linux distribution or hosting provider, install their patched package instead.
- Restart PHP-FPM, Apache or your PHP service after updating so the old workers stop running.
- If the server runs PHP 8.1 or older, plan an upgrade to a supported branch. Ask your vendor whether a backported fix is available in the meantime.
- If you cannot patch today, take the site offline or put it behind a web application firewall. Cloudflare has published managed rules for known exploit attempts, but a firewall is not a substitute for patching.
- Hide the PHP version from visitors by setting expose_php = Off in php.ini. This does not fix anything, but it stops scanners from reading your version.
- Check the server for signs of compromise: unexpected shell processes started by PHP, new files in web folders, and memory errors in PHP logs around the disclosure date.
References
This report is based only on what the homepage publicly reports. Servers behind load balancers, other subdomains, and vendor-patched builds may differ. Confirm on the server before closing the issue.
Want a second set of eyes? CTRL-A can confirm the server's real PHP build, patch it, and check for signs of compromise.
Book a call