Millions of Websites Need an Urgent Security Update: What You Need to Know

Kajan ·

A serious security flaw was found in PHP, the technology behind most websites. Attackers can use it to break into websites without a password. A fix is now available, and every PHP website should be updated as soon as possible.

In short: A serious security flaw was found in PHP, the technology behind most websites. Attackers can use it to break into websites without a password. A fix is now available, and every PHP website should be updated as soon as possible.

If your website runs on PHP, it needs a security update now. On 21 October 2026, a fix was released for two critical flaws in PHP, the language behind most of the web. Government agencies and companies around the world took their sites offline while they patched (AFP via Insider Paper).

Here is what happened, whether it affects you, and what to do.

What happened

Researchers found two serious weaknesses in PHP itself, nicknamed "PHP2Shell". PHP works like the engine under a website, so a flaw in it affects every site built on it.

Think of it as finding that a very popular brand of lock can be opened without a key. An attacker could take control of a web server without a password, then reach its files, database and customer data (Help Net Security).

The flaws were reported privately in August and kept secret while a fix was prepared. Details leaked online on 20 October, a day before the planned release. That is why so many sites went offline at once, and why attacks started before the fix was out (Patchstack).

For technical readers, the flaws are CVE-2026-109618 and CVE-2026-109619, both rated critical (CVSS 9.2).

Who is affected

Any website running an unpatched version of PHP is at risk. That includes sites built with:

  • WordPress and WooCommerce
  • Drupal and Joomla
  • Magento
  • Laravel and other custom PHP applications

The problem is in PHP, not in any one plugin or theme, so a well-maintained site is still exposed until PHP itself is updated. Researchers at Wiz say every PHP version back to 5.4 is affected by at least one of the flaws (Patchstack).

In Europe, sites including the Paris Police Prefecture, the Dutch DigiD service and Belgium's foreign ministry went offline as a precaution (AFP via Insider Paper).

Why AI is part of the story

These flaws had been hidden in PHP for decades. Security firm Calif and OpenAI reported them independently on the same day in August, and Wiz later found more ways to exploit them (AFP via Insider Paper).

Wiz researchers say turning the flaws into a working attack was close to the limit of what people could do by hand, and that advanced AI models made it far easier (Help Net Security). The number of security flaws found in 2026 is on track to roughly double last year's record.

The takeaway for website owners: old weaknesses are being found faster than ever, so updates can no longer wait for a quiet month.

The fix: what you should do now

The only real protection is updating PHP. The safe versions are 8.5.12, 8.4.27, 8.3.36 and 8.2.35, released on 21 October 2026 (Help Net Security). Security plugins and firewalls alone are not enough.

  1. Find out your PHP version. Your hosting control panel usually shows it, or ask your web developer or host.
  2. Update to a safe version. On shared or managed hosting, your host must apply the update; contact them if you are unsure.
  3. Move off old PHP. Sites on PHP 7 or 5 get no fix, because those versions are no longer supported. They need upgrading to PHP 8.
  4. Check for signs of a break-in. Attacks began before the fix was out, so look for unknown admin users or unexpected file changes.
  5. Change passwords and keys. If your site was unpatched, change admin, database and API passwords as a precaution.

If you can't update straight away, taking the site offline until you can is the safest choice. That is what many governments did this week.