Articles, , updated on

PHP flaw: how many business sites have updated?

Nine days after PHP's emergency update, 52.5% of the business sites with a visible PHP version were running a fixed version, against 43.4% a week earlier. That is what our measurements of 23 and 30 October 2026 of the same 884 sites show. Of the 515 sites without the update on 23 October, 80 had updated a week later.

What did we measure?

On Friday 23 October 2026, two days after PHP's emergency update, we fetched the homepage of 5,004 business sites once. On Friday 30 October we did it again, for the same sites and in the same way. They are the construction, installation and metalworking companies from our study of speed and WordPress. On 23 October 4,710 sites responded, on 30 October 4,717.

Many servers put the PHP version in a header of their response, X-Powered-By. Every browser receives that header but does not show it. We compared that version with the fixed versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35. There was no newer update yet on 30 October. We did not test or try anything, and we do not name any companies.

How many sites show their PHP version?

On 30 October, 28.6% of the sites that responded, 1,349 in total. Among the WordPress sites it was 39%. The other sites hide their version or do not run on PHP. So the figures below are about the sites that show their version themselves. Whether the rest have updated, we cannot see from the outside.

On 23 October there were still 903. The difference is mainly down to Plesk, a control panel that many hosting companies use. 459 sites showed a version on 30 October but not on 23 October. 424 of them run on a server with Plesk: at first the header only mentioned Plesk, a week later the PHP version as well. Why, we do not know. That is why we mainly compare the two measurements for the same sites.

How many sites have already updated?

On 30 October, 816 of the 1,349 sites with a visible version were running a fixed version: 60.5%. 160 sites (11.9%) had a version that PHP still supports, but without the update. 373 sites (27.7%) ran 8.1 or older. PHP itself no longer releases updates for those.

Bar chart: PHP version of 1,349 business websites that show their version, 30 October 2026. Already updated 60.5%, Supported version, not updated 11.9%, Version without updates from PHP 27.7%.
Of the 1,349 business websites that show their PHP version, 60.5% were running a version with the emergency update of 21 October on 30 October 2026. 11.9% had a supported version without the update, 27.7% a version for which PHP no longer releases updates. Source: MODEX's own research, free to reuse with attribution.

That share is higher than for the same sites below, because the sites that were added had more often already updated: 349 of the 459. Per sector, as a share of the sites that showed their PHP version on 30 October:

SectorUpdatedNot yet
Metalworking and machine building180 with a visible version63,3%36,7%
Construction693 with a visible version58,4%41,6%
Bouwend Nederland members204 with a visible version62,7%37,3%
Installation272 with a visible version62,1%37,9%
All sites1,349 with a visible version60,5%39,5%
All WordPress sites1,061 with a visible version62%38%

What changed in a week?

For the same sites, the share of fixed versions rose from 43.4% to 52.5%. Those are the 884 sites that showed their PHP version on both days. Of the 515 sites that had not updated on 23 October, 80 were running a fixed version a week later. 420 still showed a version number without the update. 15 no longer showed their version or did not respond.

Bar chart: share of 884 business websites with a fixed PHP version, the same sites on both days. 23 October, two days after the update 43.4%, 30 October, nine days after the update 52.5%.
For the 884 business websites that showed their PHP version on 23 and 30 October, the share with the emergency update rose from 43.4% to 52.5%. Of the 515 sites that had not updated on 23 October, 80 had updated a week later. Source: MODEX's own research, free to reuse with attribution.

A small update went faster than a switch. Of the 220 sites on a supported version without the update, such as 8.3.35, 67 had updated a week later. Of the 295 sites on 8.1 or older, 13 had: they need a newer release line. Not a single site that had already updated on 23 October showed an older version again a week later.

How are metalworking companies with WordPress doing?

On 30 October, 145 of the 398 metalworking companies with WordPress showed their PHP version. Of those, 95 had updated (65.5%) and 50 had not yet (34.5%). 31 of those sites ran a version without updates from PHP.

For the same 91 sites as on 23 October, the share that had updated rose from 51.6% to 58.2%. Of the 44 sites without the update, 6 had updated a week later. These are small numbers: with 91 sites, one site more or less already shifts the percentage by 1.1 percentage points.

How does it differ per network?

A lot, in speed too. On the 12 networks with the most sites, the share of fixed versions ranged from 0% to 78.6% on 23 October, and from 2.3% to 88.3% a week later. For each site we looked up the IP address via DNS, and via the public service of Team Cymru the network that address belongs to.

We show the networks that on 23 October had at least 40 sites, of which at least 10 showed their PHP version. For each network we compare the sites that showed their version on both days. That is why the figure for 23 October sometimes differs slightly from our first publication.

A network is not the same as a hosting company. A company's network also carries servers that customers rent and update themselves, and smaller hosting companies rent space from bigger ones. Behind Cloudflare the real server cannot be seen. And here too: a version number without the update does not always mean the site is exposed.

NetworkUpdated on 23 OctOn 30 Oct
Signet B.V.TRANSIP-AS, 461 sites, 98 with a visible version on both days73,5%75,5%
Cloudflare, Inc.CLOUDFLARENET, 439 sites, 27 with a visible version on both days51,9%55,6%
Your Hosting B.V.CLDIN-NL, 413 sites, 81 with a visible version on both days16%25,9%
Stichting DIGI NLAS-ZXCS, 229 sites, 175 with a visible version on both days0%2,3%
Hetzner Online GmbHHETZNER-AS, 158 sites, 15 with a visible version on both days40%40%
Duocast B.V.DUOCAST-AS, 130 sites, 103 with a visible version on both days78,6%88,3%
BIT BVNL-BIT, 107 sites, 20 with a visible version on both days35%40%
One.com A/SONECOM, 103 sites, 54 with a visible version on both days77,8%77,8%
Hoasted B.V.HOASTED, 72 sites, 56 with a visible version on both days48,2%83,9%
Strato GmbHSTRATO, 64 sites, 41 with a visible version on both days63,4%63,4%
Hostinger International LimitedAS-HOSTINGER, 53 sites, 29 with a visible version on both days0%65,5%
UpCloud LtdUPCLOUD, 45 sites, 32 with a visible version on both days40,6%43,8%

On 2 networks, not a single visible version was on the fixed release two days after the update. A week later it was 2.3% at Stichting DIGI NL and 65.5% at Hostinger International Limited. At Stichting DIGI NL most versions were still exactly one step before the emergency update, such as 8.3.35 instead of 8.3.36. We did not ask each company whether it has installed the update yet.

In the interest of openness: Taher, who runs MODEX, works at hosting company Cloud86. Cloud86's own website is on the network of Duocast B.V., where for the same sites 78.6% and a week later 88.3% of the visible versions had updated. We used the same measurement and the same threshold for every network, and Cloud86 did not take part in this measurement.

Is that the same 14.4% as for the WordPress updates?

No, those are two different things. In our speed study, 14.4% of the WordPress sites that show their version were missing an update of WordPress itself. That is up to the owner or the web builder. PHP runs on the server and is updated by the hosting company, or by whoever manages the server. Of the WordPress sites with a visible PHP version, 38% still showed a version number without the update on 30 October. For metalworking companies with WordPress it was 34.5%.

Which PHP versions did we see?

On 30 October, 976 of the sites with a visible version ran a release line that PHP still supports, 8.2 to 8.5. 85 sites ran 8.1, for which updates stopped on 31 December 2025. 162 sites ran 7.4, and 45 were even still on PHP 5. That last line received no more updates after 31 December 2018, according to PHP's overview.

What do these figures not tell you?

What should you do if your site runs on PHP?

Ask your hosting company whether the update of 21 October has been installed, or look in WordPress under Site Health to see which PHP version is listed. Which versions are safe and what else you can do is explained in Critical PHP flaw: do you need to act on your website?

May others use these figures?

Yes. Feel free to reuse them, with a link to this page as the source. Want a different breakdown, or the figures for a network that is not in the table? Email info@modexsoftware.nl.

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