What PHP said

On 21 October 2026 PHP published versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP’s release notes call it “a security release fixing two critical vulnerabilities (CVE-2026-109618, CVE-2026-109619) that can allow unauthenticated remote code execution”.

PHP adds: “There are no complete mitigations, updating is the only safe choice.” PHP’s announcement of 21 October 2026.

PHP’s release notes for each version:

PHP’s release of 21 October covered versions 8.2 to 8.5. PHP’s list of supported versions says which branches still receive fixes.

A version number shows a number, not whether a site has the fixes: many hosts add fixes to an older number without changing it. So our check compares versions by PHP’s numbering, and asks you to confirm with your host.

What the check reads

Only what any visitor’s browser receives from your site: its home page and the headers it sends, its certificate, its robots.txt file, the WordPress index and feed if the home page points to them, and its SPF and DMARC records. We do not log in, and we do not look for anything hidden.

Nothing runs until you confirm your email address from the link we send, and the result shows only after that.

What our check reads, and what it never does

Ask for a check

As it appears in your browser, for example www.yourbusiness.co.uk

We email you a link to confirm it. The check runs only once you press it, and nothing you type here goes in that email.

We delete a request nobody confirms after two days. The privacy notice says what we keep and for how long.