Critical PHP flaw: what to do with your website today
PHP fixed two critical security flaws today. What the flaws do, which versions get the fix and what it means for a WordPress site.
Not sure which PHP version your site runs on, or who installs the update? Call +31 6 48 65 05 83 for advice and help.
What PHP announced
On 20 October the PHP security team announced an urgent release for 14:00 UTC on 21 October. The fix came out a little earlier, just before 16:00 Dutch time.
It addresses two critical vulnerabilities, both rated CVSS v4.0 9.2. All PHP users are encouraged to prepare now so they can upgrade as soon as the release is available.
PHP security team, php.net
CVSS is the scale that gives security flaws a score from 0 to 10. Anything from 9.0 up is called critical. PHP asked everyone to prepare, so the update could be installed straight away.
These versions contain the fix: 8.5.12, 8.4.27, 8.3.36 and 8.2.35. On one of these or higher, the flaws are gone.
What the flaws do
PHP now confirms what had leaked the day before: both flaws let an attacker run code on your server remotely, without logging in. They are CVE-2026-109618 and CVE-2026-109619. Every server that handles web requests with PHP is at risk, LiteSpeed included. The announcement is on php.net.
For servers that cannot be updated straight away, PHP lists settings that lower the risk, and adds that they do not make a server safe. Only updating does. From now on anyone can see what was changed, including people who want to abuse it.
Why WordPress sites run more risk
PHP only releases security updates for versions that are still supported. Right now those are 8.2, 8.3, 8.4 and 8.5. For PHP 8.1 that stopped on 31 December 2025, for 8.0 in November 2023 and for 7.4 in November 2022.
WordPress keeps track of the PHP version of the sites that check in for updates. Today's figures:
| PHP version | Share of WordPress sites | Security updates |
|---|---|---|
| 7.4 | 16,1% | stopped Nov 2022 |
| 8.0 | 3,8% | stopped Nov 2023 |
| 8.1 | 10,7% | stopped Dec 2025 |
| 8.2 | 23,8% | until 31 Dec 2026 |
| 8.3 | 26,6% | until 31 Dec 2027 |
| 8.4 | 9,3% | until 31 Dec 2028 |
| 8.5 | 3,9% | until 31 Dec 2029 |
Source: WordPress.org and php.net, retrieved on 21 October 2026. Versions older than 7.4 together make up another 5.7%.
36%of WordPress sites run on a PHP version that gets no fix today.
WordPress itself recommends PHP 8.3 or higher. A site on 8.2 still gets this fix, but after 31 December it will not.
For 7.4, 8.0 and 8.1 PHP only published source code, for people who build PHP themselves. Some hosting companies patch old PHP versions themselves, for example through CloudLinux or TuxCare. If you are on 7.4 or 8.1, ask your host whether that applies to you. If the answer is no, or they do not know, the flaw stays on your site.
What you can do yourself
- Check which version you have. In WordPress: Tools, Site Health, the Info tab, the Server section. Otherwise in your hosting control panel (in Plesk it is called PHP Settings).
- On 8.2 or higher? Then your host usually installs the fix itself. From tomorrow, check that you are on 8.2.35, 8.3.36, 8.4.27 or 8.5.12 (or higher), and ask if you are not.
- On 8.1 or lower? Then you need to move to a newer version, preferably 8.3 or 8.4. Make a backup first and update WordPress, your theme and your plugins.
- Try the new version on a copy first if your host offers a staging environment, and go through your forms, your shopping cart and your login there.
This is where it goes wrong. PHP 8.0 removed functions that old plugins still use, such as create_function() and each(). After the switch such a plugin causes a fatal error, and WordPress shows nothing but a message about a critical error. In most control panels you switch back to the old version with one click, and the error in your hosting log tells you which plugin it was.
What we do
Burgmedia.eu itself runs on PHP 8.5. Our host installed the fix the same evening: since 21 October it runs on 8.5.12.
For clients, and for anyone who gets stuck, we check which PHP version the site runs and what the host does. If you need a newer version, we put it on a copy of your site first, fix the plugins or theme code that break, and only then switch your real site over. After that we keep an eye on the error log.
If you are on 8.2 or higher and your host updates PHP itself, you do not need us. Just check that it happened.
Not sure whether your site is affected, or running an old version? Call +31 6 48 65 05 83 and we will look at it straight away.
The fix is out. Look up your version number and check whether it has been updated.
Want us to take care of it? Updating your PHP version.