Home/Blog/Critical PHP Flaws: Protect Your WordPress Site Now

Critical PHP Flaws: Protect Your WordPress Site Now

critical PHP flaws WordPress security 2026

On 21 October 2026, the PHP team released an emergency security update for two critical vulnerabilities in PHP itself. Both flaws let an attacker run code on a web server without logging in, and security researchers quickly nicknamed the issue PHP2Shell. Because every WordPress site runs on PHP, every WordPress site was potentially at risk until its server moved to a patched version.

If you run a WordPress site, this update matters even when your plugins and themes are fully up to date. The flaws are not in WordPress core, a plugin, or a theme. They sit in the PHP runtime underneath WordPress, so only a PHP update, or a confirmed vendor patch, closes the hole.

What Are the Two Critical PHP Flaws?

The first flaw, CVE-2026-109618, sits in how PHP handles running out of memory in the middle of a request, for example during a file upload. Memory that was never properly set up can be cleaned up anyway, and it can contain attacker-controlled data.

The second flaw, CVE-2026-109619, lets leftover state from one crashed request leak into the next request handled by the same PHP worker. The confirmed attack paths run through the session upload progress feature of PHP.

Both flaws scored 9.2 out of 10 on the CVSS severity scale, placing them in the critical category. CERT-EU issued a critical advisory on the same day the fixes shipped, and proof-of-concept exploits were already reported to be circulating, which is why waiting was never a good option.

Which PHP Versions Fix the Problem?

The patched releases are PHP 8.5.12, PHP 8.4.27, PHP 8.3.36, and PHP 8.2.35. If your site runs one of these versions or later, it includes the fix for both flaws.

PHP 8.1 and older branches no longer receive regular upstream security releases. Some vendors backport the fixes into their own packages, so a version number alone does not always tell the full story. If your version looks old, ask your host whether they have applied the fix.

How to Check Your PHP Version

In WordPress, open Tools, then Site Health, then the Info tab, and expand the Server section. Your PHP version is listed there. Many hosting panels also show the PHP version on the main dashboard or under a PHP settings page.

updating PHP version in hosting control panel

How to Update PHP on Your WordPress Site

Start with a full backup of your site, including the database. Then open your hosting panel, find the PHP version selector, and choose a patched release from the list above. Save the change, let the server restart PHP or rebuild the container, and then test your site carefully, starting with the homepage, login page, and any contact or checkout forms.

If your hosting panel has no PHP selector, send your host a short message naming both flaws, CVE-2026-109618 and CVE-2026-109619, and ask them to move your site to a patched PHP version. On managed hosting, this fix may already be applied, but get the confirmation in writing rather than assuming it.

What If Your Site Runs PHP 8.1 or Older?

Plan an upgrade to PHP 8.2 or newer as soon as possible. Before switching, check that your theme and plugins support the newer version, and test the change on a staging copy of your site if your host offers one. Most modern themes and plugins already support PHP 8.2 and 8.3, so the upgrade is usually smooth.

Important: Updating WordPress Does Not Fix This

Updating WordPress only replaces WordPress files. It does not change the PHP version on your server, because PHP is separate server software controlled by your hosting account. You need both: an updated WordPress install and a patched PHP version. If you only do one, the other gap stays open.

If you manage several sites, bookmark KamiWeb’s free tools, WordPress themes, and plugins pages to speed up routine site checks.

Quick Protection Checklist

  • Check your PHP version in Site Health today.
  • Move to PHP 8.5.12, 8.4.27, 8.3.36, or 8.2.35.
  • Back up before changing anything.
  • Test your site after the switch.
  • Keep WordPress, themes, and plugins updated as well.

Frequently Asked Questions

Do I need to take my site offline?

No. Sites on a patched version, or confirmed protected by their host, do not need to go offline because of this disclosure. Only unpatched sites that cannot be fixed quickly were advised to consider temporary isolation.

Will updating PHP break my site?

Rarely, if you back up first and test after. Very old plugins or themes can struggle with newer PHP, which is why a staging test is worth the extra few minutes.

How do I know my site is protected?

Confirm the PHP version in Site Health matches a patched release, or get written confirmation from your host that both flaws are patched on your server.

The PHP2Shell flaws were a reminder that WordPress security does not stop at WordPress itself. The fix takes minutes, the risk of ignoring it is unauthenticated code execution, and the check is free. Open Site Health today, confirm your PHP version, and patch it if you are behind. Your future self will be glad you did.