Skip to content
Free · Seconds · No email

Is your website affected by the PHP flaws?

On October 21, 2026, the FBI's Cyber Division warned about two critical flaws in PHP, the code under WordPress and a big share of the web. Type your website below. In a few seconds you will see whether it runs PHP, which version it announces, and exactly what to tell whoever runs it.

Check my site
A mustard seed character in a cap guards a golden vault with a ring of keys and a padlock.
Free

Seconds // no email

Check your website.

We ask for your homepage once, the way any visitor's browser does, and read what it sends back. Nothing else is touched.

The fix

One update. Every server.

PHP's own advisory says there is no complete workaround: updating is the only safe choice. Find your branch, then the release it needs.

Your branchFixed in
PHP 8.58.5.12
PHP 8.48.4.27
PHP 8.38.3.36
PHP 8.28.2.35
PHP 8.1 and olderNone

On WordPress?

Read the exact version yourself in two minutes.

  1. 1Log in to WordPressSign in to your site at yoursite.com/wp-admin.
  2. 2Open Site HealthIn the left menu, open Tools, then Site Health.
  3. 3Read the PHP versionOpen the Info tab, expand Server, and read the PHP version.
  4. 4Compare itPatched releases are 8.5.12, 8.4.27, 8.3.36, 8.2.35. Lower on the same branch, or 8.1 and older, means it needs the update.

Why our sites had nothing to patch

You shouldn't have to know what PHP is.

You should know if ChatGPT knows your name.

We don't build on PHP. We build every page for Google and AI to read, manage the site for you end to end, and check what the AI assistants say about you. A week like this one costs our clients nothing.

Questions

What owners ask us.

Is running this check safe for my website?

Yes. We ask for your homepage once, the same way any visitor's browser does, and read what it sends back. We never touch a login page, an admin page or anything but the address you type.

How can you tell which PHP version my site runs?

Many servers announce it in a header called X-Powered-By, for example "PHP/8.1.34". When yours does, we show you that exact header. When it does not, we look for the things PHP sites leave behind: a WordPress, Drupal or Joomla signature, a PHP session cookie, or links to .php pages on your own domain.

My site says "no sign of PHP." Am I safe?

From these two flaws, probably, but a site can hide what it runs on, so it is not a guarantee. If you are not sure, ask whoever hosts your site what it runs on and get the answer in writing.

My host says they backported the fix. Does that count?

It can. Linux distributions and some hosts apply the fix without changing the version number, and PHP published minimal fixes for 7.4, 8.0 and 8.1. A version number cannot show that, so ask your host to confirm in writing that the fixes for CVE-2026-109618 and CVE-2026-109619 are installed.

My site is on Wix, Squarespace or Shopify. Do I need to do anything?

No. Those platforms run their own servers and you cannot change PHP on them. These two flaws are theirs to handle, not yours.

Cloudflare sits in front of my site. Does that protect me?

It helps. Cloudflare has published stopgap firewall rules for these flaws. They do not replace the update, which PHP's advisory calls the only safe choice.

Do you keep what I check?

We keep the address you checked and what its homepage announced, so the checker can limit how often it runs. Your own IP address is never stored, only a scrambled code made from it.

Why don't your sites run on PHP?

We build on a modern stack with no PHP server for an owner to patch, and we manage every site for our clients, end to end. A week like this one costs them nothing. The time goes where it should: getting found on Google and in AI answers.