Two critical PHP flaws, CVE-2026-109618 and CVE-2026-109619, let attackers run code on unpatched servers, and they are being exploited right now. Enter your web address for a free, instant check.
A well run server hides its PHP version, so the check above can't always tell. Pick where your site is hosted, follow the steps, then enter the version you find and we'll tell you whether you're covered.
If your site came back vulnerable, or you would rather not touch PHP yourself, we can take care of it. Xigen looks after development and hosting for businesses across the UK, which includes keeping PHP patched and tested without breaking the site it runs on.
Send us the address and we'll take a look.
Email info@xigen.co.ukPHP2Shell is the name for these two flaws, disclosed on 21 October 2026. Both are rated 9.2 (CVSS v4.0) and let an unauthenticated attacker run code on the server. Every PHP release from 5.4 through 8.5.11 is affected.
A well configured server hides its PHP version, so this tool often cannot read it from outside. An undetermined result is not an all clear and not a fault. It means the only reliable check is on the server: run php -v, or use the platform guide above.
Update PHP. The flaws are fixed in 8.5.12, 8.4.27, 8.3.36 and 8.2.35. If you use your operating system's package manager, apply your vendor's updated packages.
There is no complete mitigation. Updating is the only safe fix. As interim hardening you can set session.upload_progress.enabled = Off, set fatal_error_backtraces = Off on PHP 8.5, and set pm.max_requests = 1 on your FPM pools. Those reduce the attack surface for CVE-2026-109619 only.