Skip to content
Security

PHP Ships Emergency Fix for Two Critical Flaws: Updating WordPress Won’t Protect You This Time

3 min read

On Wednesday, October 21, 2026, the PHP project released an emergency security update. It fixes two critical flaws, CVE-2026-109618 and CVE-2026-109619, both rated 9.2 out of 10 on CVSS v4.0. Both can allow unauthenticated remote code execution. The key point for site owners: the bug is in PHP itself, underneath WordPress, plugins and themes. Updating WordPress does not protect you.

What happened

According to an analysis by Codeable and a notice from GoDaddy, the fix was released on October 21 at 14:00 UTC. Codeable states that details leaked and early attacks were reported before the fix shipped. Treat that part with care, since it comes from one source, but the advice is the same everywhere: patch as soon as possible.

Both sources also agree that WordPress.org does not plan a WordPress update, because none is needed. The fix lives at the server level.

Which PHP versions are fixed

  • PHP 8.5: 8.5.12
  • PHP 8.4: 8.4.27
  • PHP 8.3: 8.3.36
  • PHP 8.2: 8.2.35

Official fixes exist only for the 8.2 branch and newer. There is no official fix for PHP 8.1 and older. Those sites are safe only if the host or Linux distribution has backported the fix. Note that a backport often leaves the visible version number unchanged, so a patched server may still report something like 8.5.11. Do not rely on the version string alone; ask your host about the build date.

How to check whether you are exposed

In WordPress you can see the PHP version under Tools → Site Health → Info → Server, or in your hosting control panel. Then act according to your hosting type:

  • Managed WordPress hosting: the provider updates PHP. Just confirm they have. GoDaddy, for example, says it patched its managed hosting on the evening of October 21.
  • Shared hosting: the host applies the fix. Ask whether it is done, especially if you run PHP 8.1 or older.
  • VPS and self-managed servers: it is on you or your server admin. Install the updated PHP packages and restart PHP so every worker runs the fixed version. Verify with php -v.

Temporary mitigations and a second, still unpatched issue

PHP also published temporary mitigations but describes them as incomplete. For example, setting session.upload_progress.enabled = 0 blocks one attack path for CVE-2026-109619. WordPress does not use that feature, so it can be switched off without impact, but test file uploads afterwards. Only updating gives full protection.

On Thursday, October 23, a third, lower-risk issue was added, CVE-2026-115560. According to GoDaddy it is not yet patched; the fix will come in the next routine release. The recommended mitigation is the same session.upload_progress.enabled = 0 setting.

Old PHP: time to move

If you run PHP 8.1 or older, this is a strong reason to move to 8.2 or newer. Older themes and plugins may break, so take a full backup, try the upgrade on a staging copy first, and only then switch the live site. If you manage your own server and cannot update PHP quickly, Codeable reports that WordPress.org and the UK’s NCSC suggest taking the site offline until it is fixed.

Conclusion

Do three things today: find out where PHP runs, confirm with your host or admin that the October 21 fix is in place, and plan your exit from old PHP versions. If you are unsure, get in touch. We are happy to check your PHP version, server settings and update status.

Sources: Codeable, GoDaddy (published October 20–24, 2026).

Potřebujete pomoc s webovým projektem?

Rádi vám pomůžeme. Konzultace je zdarma a nezávazná.

Poraďte se s námi
Let's collaborate

Tell us about your project

Describe your project and we'll get back to you.

50+ satisfied companies
We reply within 24h
Free consultation
Bc. Martin Procházka
founder & developer
Please enter your name.
Please enter a valid email address.
Please enter a valid phone number.
Please describe what you need.
You must agree to the processing of personal data.