On 21 October 2026 PHP fixed two critical vulnerabilities that can let attackers take over a website without logging in. Enter your website address to see which PHP version it shows and whether it needs an update.

We load your public home page once, like a browser, and read the PHP version your server announces. Nothing is stored.

Which PHP versions are safe?

  • PHP 8.5.12, 8.4.27, 8.3.36, 8.2.35 or newer in the same branch: fixed.
  • Older releases in those branches: update now, then restart PHP.
  • PHP 8.1, 8.0, 7.4 and older: no official fix, plan an upgrade to PHP 8.3 or 8.4.
  • PHP 8.2 reaches end of life on 31 December 2026.

Frequently asked questions

How does the PHP version checker work?

It loads your public home page once, like a normal browser, and reads the PHP version your web server announces in its X-Powered-By header. It compares that version with the releases that fixed CVE-2026-109618 and CVE-2026-109619: PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35.

It says "not visible from outside". Am I safe?

Not necessarily. Many well-configured servers hide their PHP version, which is good practice, but it means the check cannot see it. Look up the real version in your hosting panel, WordPress Site Health or a phpinfo page, or ask us to check it for you.

My server shows an old version but I installed updates. Why?

Linux distributions such as Ubuntu, Debian and Red Hat often patch security bugs without changing the main version number. Check your vendor security notice for the two CVE numbers, and make sure PHP-FPM or Apache was restarted after the update.

Do you store the websites I check?

No. The check runs once and the result is shown only to you. We record anonymously that a check was run and its result type, to improve the tool.

Emergency PHP security update service · PHP vulnerability October 2026: what to do now · AI App Health Check