PHP after the October fixes: what changed on Latvian sites
On 21 October, PHP released fixes for two critical vulnerabilities. At the end of the month I checked Latvian sites whose PHP versions I had recorded in September. Among sites with a version visible on both visits, 41.1% now report a fixed release or a newer one. If your site runs PHP, check its full version and ask who maintains the build. 7.4 or 8.3 on its own is not enough to establish whether the fix is present.
The first check was on 25 September; the second ran overnight on 29–30 October. More than a month separates them. I cannot attribute every version change to the 21 October advisory. But the fixed October releases did not exist before that date, so seeing one in the second check does tell us something.
1,480 sites reached a fixed release
I checked 30,161 sites. A PHP version appeared in both checks for 3,598 of them. That is the group where a before-and-after comparison is possible. Among those sites, 1,681 reported a higher number. Separately, I counted 1,480 whose new number reached a release with the October fixes or a newer one.
Choose the PHP branch reported in September. The figure shows how many sites stayed on that branch and where the others moved. No site names are shown.
All the numbers as a table
| Change between checks | Sites | Of 3,598 |
|---|---|---|
| Reached a fixed release or newer | 1,480 | 41.1% |
| Version number did not change | 1,907 | 53.0% |
| Number changed, but no fixed release was visible | 211 | 5.9% |
Some common transitions were 8.3.33 → 8.3.36 on 445 sites, 8.2.33 → 8.2.35 on 264 and 8.4.25 → 8.4.27 on 101. The newer numbers in those pairs include the fixes for CVE-2026-109618 and CVE-2026-109619. Updating within a branch is generally a smaller change than moving an entire project from PHP 7 to PHP 8, though its code and plugins still need checking afterwards.
A missing version number is not an update
In September, 6,219 sites disclosed PHP. The new check found a version on 3,942. Subtracting those figures does not tell us how many sites stopped using PHP. Another 2,373 sites returned a successful page response in October but no longer disclosed a PHP number in the response header. A server can hide that header without updating PHP.
The reverse also happened: 344 sites disclosed a version only on the second visit. That does not prove they had just installed PHP. A response header is what a server says about itself, not an inventory of its installed packages.
An unsupported branch may still have a vendor patch
Of the 3,942 sites currently disclosing a PHP version, 2,095 report a branch that the PHP project no longer supports. That is 53.1% of visible versions, not half of all Latvian sites.
An old number, however, does not by itself prove that the running build lacks a fix. A hosting vendor can backport a patch to its own PHP build while retaining the old branch number. After the October release, the PHP team even provided minimal source backports for 7.4, 8.0 and 8.1 for people building from source or using a long-term support vendor.
For a project that cannot yet run on PHP 8, that can buy time. On a virtual server, an administrator could build a patched PHP release into a new Docker image. A newer image alone proves nothing about the PHP patch: check which fixes it contains, who maintains the build and which image is actually running. Moving to a supported branch remains a sensible longer-term plan.
Check the full version on your site
Your hosting panel may show the PHP version. In WordPress, look under Tools → Site Health → Info → Server. For the two October vulnerabilities, ordinary PHP releases need at least 8.2.35, 8.3.36, 8.4.27 or 8.5.12. If your number is lower, check the origin of that particular build and its patch record.
You can send your host or server administrator one question: “Which PHP build is running on my site, and does it include the fixes for CVE-2026-109618 and CVE-2026-109619? If PHP runs in a container, which image is deployed?” The answer needs to describe the running server, not merely an update offered in the control panel.
You can also compare your release and its official support period in the PHP version checker. Hiding a header does not fix PHP. If you cannot change branch yet, ask for a documented patched build and a migration plan.
Sources and scope of the check
- My check covered 30,161 sites in a working sample of Latvian websites. The first visit was on 25 September 2026; the second on 29–30 October. I read PHP numbers from server response headers. A number appeared on both visits for 3,598 sites, and only those sites are in the change figures. The sample does not represent every Latvian site. A header cannot show vendor backports or prove that a site is vulnerable or safe.
- PHP's 21 October security notice — fixed releases and source backports for older branches.
- PHP support dates and end-of-life branches.
- CVE-2026-109618 advisory and CVE-2026-109619 advisory.
If you need to find out which PHP build actually runs your site and whether it contains the fixes, get in touch.