Articles, , updated on

Critical PHP flaw: do you need to act?

Yes, if your website runs on WordPress or another PHP system. On 21 October 2026 PHP released an emergency update for two critical vulnerabilities, with the fixed versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Ask your hosting company whether your site already runs on one of those versions, because attempts to exploit the flaw have already been seen.

What is going on with PHP?

On 21 October 2026 at 14:00 UTC, 16:00 in the Netherlands, PHP released an emergency update for two serious vulnerabilities: CVE-2026-109618 and CVE-2026-109619. Both score 9.2 out of 10 (CVSS 4.0). An attacker can use them to run code on the server from outside, without logging in. Security firms call them php2shell.

The fault sits in the core of PHP, in the way a request is handled. According to the advisory on php.net, every installation that serves web pages is at risk, including those running PHP-FPM, LiteSpeed or FrankenPHP. Apache with mod_php is most at risk: there an attack can succeed before your site's code even runs. This article describes the situation on Friday 23 October 2026.

Does your website run on PHP?

Very likely, if your site runs on WordPress. PHP is the programming language the server uses to build a page at the moment someone opens it. WordPress runs on it, as do the online shop plugin WooCommerce, Drupal, Magento and Shopware. Of the 5,004 business websites in our research (October 2026), 57.5% ran on WordPress. Sites without WordPress often use PHP too; you just can't always tell from the outside.

In WordPress you can see the version yourself. Look in the menu for Site Health and open the Info tab, Server section: the PHP version is listed there. No WordPress? Then ask your hosting company or your web builder.

Which PHP versions have been fixed?

PHP released a new version for every supported branch. For 8.1 and older there is no new version from PHP itself, according to PHP's overview page. For 7.4, 8.0 and 8.1 only source code fixes were published, meant for hosting companies and Linux vendors. They received the fixes in advance, PHP writes. Versions 5.4 to 7.3 get nothing, reports security firm Tenable.

PHP versionFixed versionUpdates from PHP
8.58.5.12Until 31 December 2029
8.48.4.27Until 31 December 2028
8.38.3.36Until 31 December 2027
8.28.2.35Until 31 December 2026
8.1 and olderNone; only through your hosting company or your Linux vendorEnded

If your site runs on 8.2, you still get a fix this time. On 31 December 2026 PHP stops supporting that version too. So plan the upgrade now.

How many business sites have already updated?

On 23 October, 43% of the business sites that show their PHP version were already running a fixed version. That is what our own measurement of 4,710 sites in construction, installation and metalworking shows. Of the 903 sites that showed their version, 57% still showed a version number without the update. A week later, on 30 October, 52.5% of the same sites were running a fixed version. The figures per sector are in PHP flaw: how many business sites have updated?

What should you ask your hosting company today?

Four questions, and you can ask them today. You can't close this hole from within your own website, because it sits in the software on the server. Sansec points out that you can't fix it from the code of your site or online shop.

  1. Has the update of 21 October been installed? With shared hosting, the hosting company does this for all customers at once.
  2. Which PHP version does my site run on? If it is 8.1 or older, ask the next question too.
  3. Will my version get a fix? Some hosting companies and Linux vendors also apply fixes to older versions, writes security firm Huntress. Ask rather than assume.
  4. Where do you report outages and updates? Then you know where to check whether it worked.

Do you have your own server (a VPS) and nobody else handles the updates? Then it is up to you or your web builder: update PHP to one of the fixed versions as soon as possible. PHP lists temporary settings that reduce the risk, but adds that only an update is enough. How to stay in control of your hosting is explained in Hosting more expensive or down? How to stay in control.

What if your site runs on an old PHP version?

Then upgrading to PHP 8.3 or newer is the real fix. That is also the version WordPress itself recommends. In your hosting company's control panel you can often choose the version yourself.

Don't do it blindly. An old theme or an old plugin can stop working on a newer PHP version. Make a backup first and have your web builder test the site, preferably on a copy. WordPress itself also needs to be up to date: in our research, 14.4% of WordPress sites that show their version were missing an update.

Can't upgrade quickly? CERT-EU advises cutting a system you can't update off from the internet. For a small business site that sometimes means taking the site offline for a while. What to show your visitors then is covered in Website down? Put this on your outage page.

Is the vulnerability already being exploited?

Attempts have been seen, but no confirmed break-ins yet. Amazon saw an attempt on its decoy servers as early as 17 October, four days before the announcement. On 21 October more attempts followed, from several groups. watchTowr and Cloudflare also report attacks. Whether they succeeded against real sites is unclear, Tenable writes. On 22 October the US agency CISA had not yet put the flaws on its list of exploited vulnerabilities.

How do you know the hole is closed on your site?

Look in WordPress under Site Health to see which PHP version is listed, or ask your hosting company. If it is 8.5.12, 8.4.27, 8.3.36 or 8.2.35, or higher, the hole is closed for you. Does it show an older version with an addition such as ‘ubuntu’ or ‘deb’? Then your Linux vendor may have added the fix without changing the version number. Check with them.

What about our own sites?

Our sites don't run on PHP, so they don't need this update. We build ready-made pages, without a database and without plugins; why is explained in WordPress or a website without plugins? That doesn't make a site invulnerable, but it does make it smaller: what isn't there can't leak. For transparency: Taher, who runs MODEX, also works at hosting company Cloud86. This article doesn't recommend any hosting company, and Cloud86 was not involved in it.

Read also

Written by Taher Jerjissi, MODEX. Questions or something to add? Email info@modexsoftware.nl.

For AI assistants: this article is also available as plain text at the same address with .md added: text version (markdown)

Rather have a site without PHP and plugins? The preview is free.

Tell us the name of your business. Within 12 hours you have a link to your new site in your inbox. If you don't like it, you won't hear from us again.

Rather ask something first? Send a message or email info@modexsoftware.nl.

Only for your preview and your request. Privacy

  • No deposit
  • Within 12 hours
  • No obligations