Skip to main content

Free security check

Is your website affected by the PHP vulnerability?

Two critical flaws in PHP itself, CVE-2026-109618 and CVE-2026-109619, were fixed on 21 October 2026. Enter your website and we’ll read the PHP version it reports.

This checker reads the PHP version your website reports about itself and compares it with the releases that fixed two critical PHP flaws on 21 October 2026. It requests your homepage once, reads the response headers and nothing else, and stores nothing. It can’t prove your site is safe or exposed, and it says so on every result. What it gives you is a fast first read and the right questions to put to your host. For the background, read our guide to the October 2026 PHP flaws.

What happened

On 21 October 2026 the PHP project released fixes for two flaws in PHP itself, tracked as CVE-2026-109618 and CVE-2026-109619. The PHP security team rates both 9.2 (critical) on the CVSS 4.0 scale, and the National Vulnerability Database gives them 9.8 on the older CVSS 3.1 scale. Both can allow remote code execution with no login, meaning someone outside your business could get your server to run instructions of their choosing.

PHP’s announcement says the risk covers all PHP installations serving web requests, whether through Apache with mod_php, PHP-FPM, FrankenPHP or LiteSpeed. It rates mod_php highest, because a working exploit was shown against it that runs before any of the site’s own code. For PHP-FPM, the security team’s analysis points to the same weakness without a complete exploit having been shown.

Because the flaw sits in PHP and not in a plugin or theme, a WordPress site can have every plugin up to date and still be exposed. On 26 October 2026 CISA, the US government’s cyber security agency, added both flaws to its Known Exploited Vulnerabilities catalogue, which means it has evidence they are being used in attacks. If your site is not on a fixed version yet, treat the update as urgent.

Affected and fixed versions

PHP branch Affected First fixed version
8.5 before 8.5.12 8.5.12
8.4 before 8.4.27 8.4.27
8.3 before 8.3.36 8.3.36
8.2 before 8.2.35 8.2.35
8.1, 8.0, 7.4 yes no new release; source-only patches published
7.3 and older no longer supported no fix from the PHP project

PHP 8.1 and older no longer get releases from the PHP project. For this incident the security team published minimal source patches for 7.4, 8.0 and 8.1, and Linux distributions and long-term support vendors were sent the fixes in advance. Because none of those is a new release, a patched legacy build still reports its old version number. That is why the checker marks every legacy version as “can’t tell from outside”.

Who’s most at risk

Sites on old PHP are the obvious group. Anything on 8.1 or earlier has been outside official support for a while, and whether it has this fix depends entirely on who built that copy of PHP and whether they applied the patch.

The other group is sites on servers someone manages themselves: a virtual server set up by a past developer, or a box nobody has logged into for a year. On managed hosting, the host updates PHP. On a self-managed server, nobody does unless it’s someone’s job.

How to check yourself

The checker reads the version your site advertises. To see what the server is running, ask whoever has access to your hosting.

  1. If your host gives you SSH or a web terminal, run php -v. The first line shows the version and the date that copy of PHP was built.
  2. In WordPress, go to Tools, then Site Health, then the Info tab, and open Server. The PHP version is listed there.
  3. Compare the version with the table above.

On a legacy branch, the build date in php -v helps. A build dated before 21 October 2026 can’t contain this fix. A later date means it might, and only the host can tell you whether the patch went in.

Keep in mind that php -v on the command line can be a different PHP from the one serving your website. Site Health shows the one your site uses.

What to ask your host

Send these three questions, in writing:

  1. Which PHP version is my site running?
  2. Has the 21 October 2026 PHP security update (CVE-2026-109618 and CVE-2026-109619) been applied, and when?
  3. If the site is on PHP 8.1 or older, when will it move to a supported version?

A good host will answer all three in one reply. If you get a vague answer, ask again for the version number and the date.

If you can’t patch yet

Updating PHP is the only complete fix. The PHP advisories and PHP’s announcement are clear on that, and they list some interim settings that reduce exposure to the paths they’ve confirmed. Each one has a cost, and none of them makes a server safe.

For CVE-2026-109618 (GHSA-w8hw-w9fx-j79w):

  • Set memory_limit=-1 at server level, so the site can’t override it, and restart PHP. With no limit, one runaway script can use as much memory as the server has, and the advisory warns that a memory failure underneath PHP can still reach the flaw.
  • Keep post_max_size low: 8M if the site takes no uploads, 32M if it does, with upload_max_filesize below it. Larger uploads will then fail.
  • Limit request size, field counts and multipart parts at the web server in front of PHP.
  • Don’t swap in RLIMIT_AS or RLIMIT_DATA limits. The advisory says they can cause the very memory failure the flaw needs.
  • Don’t rely on a container memory cap. The advisory says it isn’t a guaranteed fix and can take down every PHP worker at once.

For CVE-2026-109619 (GHSA-6wmf-4rv5-p3rp):

  • Set session.upload_progress.enabled=0 in php.ini or the pool config, then restart every worker. Anything using PHP’s upload progress tracking stops reporting progress, and the advisory says this blocks the confirmed paths but not every variant.
  • On PHP 8.5, set fatal_error_backtraces=0.
  • Remove invalid or deprecated PHP settings that produce warnings on every request. Hiding the warnings doesn’t help.
  • The advisory suggests considering pm.max_requests=1 for PHP-FPM, which restarts each worker after one request and will slow the site.

If any of that reads like a foreign language, it’s a job for your host or developer, and the update is still the thing to ask for.

Frequently asked questions

Does a patched version number mean my site is safe?

It means the PHP your site reports includes the fix. It doesn’t prove the reported version is the one serving every request, and it says nothing about other weaknesses. Your host can confirm the rest.

My site hides its PHP version. Is that a problem?

No, hiding it is good practice, because it stops scanners matching your site to a known flaw. It does mean nobody can check the patch from outside, so ask your host directly.

Why can’t you tell on PHP 8.1 or older?

The fixes for 8.1, 8.0 and 7.4 were published as source patches with no new release number. A patched build and an unpatched one report the same version, so only the host can confirm.

Does this check test my site for the vulnerability?

No. It makes one normal request for your homepage and reads the headers that come back. It doesn’t try any exploit or send anything unusual, and it doesn’t request any other page.

Do you keep the sites people check?

No. The address you enter and the result are not logged or stored. If you share a result link, the check runs again when someone opens it.

Want someone to check it properly?

A version header is a clue, not an answer. If you’d like a person to confirm where your site stands, ask for a free mini audit and tell us you came from this check. If nobody looks after your hosting at all, that’s the bigger problem, and it’s what our support retainers and WordPress work cover. The checker is one of our free tools.

Portrait of Alexander De Sousa, founder of Digital Royalty
Founder-led
“I’ve put everything I know into how this company works — the standards, the method, the care on every project. It runs through the whole team, and I hold us all to it.”

Alexander De Sousa · Founder LinkedIn

Featured on BBC Radio Solent

Get started

Tell us what you need

A few quick questions, then a straight answer from a real person — usually within a few hours.

What happens next

  1. 1 We reply A real person reads your answers and gets back to you, usually within a few hours.
  2. 2 Questions or a short call If anything isn't clear, we ask by email or book a short call. Before any call we audit your website and make the quick fixes it finds, free.
  3. 3 Your fixed quote A clear, fixed price in writing, within 48 hours of any call. There is no obligation to go ahead.

Tell us what you're working on

Whether it's a new site, a platform, or a process that shouldn't be manual any more — we'll tell you honestly if we can help.