GuideTech & AI

PHP Critical Security Patch: What to Do About the Two New RCE Flaws

PHP is shipping emergency fixes for two critical flaws that could let attackers take over web servers, and details leaked early. Here's who's affected, how to check your PHP version, and what WordPress site owners should do today.

PHP vulnerabilities

PHP, the programming language behind WordPress and much of the web, is releasing emergency security patches today, Wednesday, October 21, 2026, at 14:00 UTC (10 a.m. Eastern, 7 a.m. Pacific). The patches fix two critical flaws that could let attackers run their own code on a web server, and details about them leaked online a day early.

If you run a website, especially a WordPress site or online store, this matters right now. Security researchers expect attackers to start scanning for vulnerable servers within minutes of the release. And sites running older PHP versions may not get a fix at all.

What are the new PHP vulnerabilities?

The two flaws are tracked as CVE-2026-109618 and CVE-2026-109619. (A CVE is the standard ID number for a publicly known security bug.) Both are remote code execution, or RCE, vulnerabilities. That means an attacker could potentially run commands on your server over the internet, without needing a password.

The PHP security team rated both flaws 9.2 out of 10 on the CVSS scale, the standard severity score for security bugs. Some early posts online claimed a perfect 10.0, but 9.2 is the official rating.

The bugs sit in PHP core, the language itself, not in a single plugin or app. That’s why they’re so serious: any website or app built on an affected PHP version could be exposed.

Related: Flock Cameras: How They Work and What the Recent Hack Revealed · Gemini AI Hack: How Google’s AI Breached Three Real Companies · Outlook Outage: Microsoft Investigates Email Problems Affecting Thousands of Users

Why are the patches coming out early?

The plan was to release fixes quietly under a coordinated disclosure, where details stay private until patches are ready. That plan fell apart on October 20, when news of the bugs leaked online before the fixes were out.

Here’s how it unfolded:

When (UTC)What happened
October 20, about 15:20A Hacker News post warned of two upcoming PHP RCE disclosures
October 20Security firm watchTowr confirmed the flaws are real and reproduced one of them
October 20A screenshot of an exploit tool called “PHP2Shell” circulated online
October 20The PHP team announced an emergency security release
October 21, 14:00Scheduled release of the fixes and full technical details

The PHP team said it may release even sooner if technical details go public or attacks begin. As of October 20, security firm Huntress said it had not yet seen the flaws being exploited in the wild.

Which PHP versions are affected?

Reports say the flaws go back to PHP 5, which covers versions released as far back as 2004. The PHP team says it will publish the exact list of affected and fixed versions with today’s release.

The bigger problem is that only supported versions of PHP are expected to get fixes. Security firm Mallory reports that patches will cover PHP 8.2 and newer. Some early reports said 8.0 and newer, so check the official release notes once they’re out.

Based on current reporting, here’s where each version likely stands:

PHP versionStill supported?Expected to get a fix?What to do
PHP 8.3, 8.4, 8.5YesYesUpdate as soon as the patch is released
PHP 8.2Security fixes only, until end of 2026YesPatch now, then plan an upgrade to 8.3 or newer
PHP 8.0 and 8.1No (end of life)Not expectedUpgrade to a supported version
PHP 7.xNo (end of life)NoUpgrade urgently
PHP 5.xNo (end of life)NoUpgrade urgently

That leaves a lot of servers exposed. Mallory counted about 884,000 internet-facing hosts running PHP versions that won’t get a fix, including about 369,000 on PHP 5 and 329,000 on PHP 7.

Is your WordPress site affected?

Quite possibly. As of September 27, 2026, 37.6% of WordPress sites reporting to WordPress.org ran a PHP version that had already reached end of life. About 16.7% were still on PHP 7.4, which stopped getting updates in November 2022.

Here’s how to check your PHP version in WordPress:

  1. Log in to your WordPress dashboard.
  2. Go to Tools, then Site Health.
  3. Click the Info tab and open the Server section.
  4. Look for PHP version.

You can also find it in your web host’s control panel, usually under a section called PHP settings or PHP configuration.

What should you do right now?

The fix has to happen at the server level, not inside WordPress, so how you handle it depends on your hosting.

  • If you use managed or shared hosting: Most hosts apply PHP security patches for you. Check your host’s status page or support account today to confirm they’re updating. If your site is on PHP 8.1 or older, switch to PHP 8.3 or newer in your hosting panel.
  • If you manage your own server: Update PHP as soon as the release is out, through your operating system’s package manager or official PHP builds. Prioritize servers that face the public internet.
  • If you’re on an old PHP version: Don’t wait. Back up your site, then test the newer PHP version on a staging copy if your host offers one. Old plugins are the most common thing that breaks during a PHP upgrade, so update your plugins and themes first.

Security firm Sansec warned it expects mass attacks within 15 minutes of the release, once attackers can study the published fixes. That’s why speed matters more than usual with this one.

My take: if your site still runs PHP 7, this is the push to finally upgrade. Upgrading isn’t just safer. Moving from PHP 7.4 to PHP 8.3 has been shown to make WordPress handle roughly 14% to 20% more requests per second.

What to Watch Next

  • PHP security release (October 21, 2026, 14:00 UTC): The exact fixed version numbers and technical details arrive with the release.
  • First reports of attacks (expected within hours of the release): Watch security firms like Sansec, Huntress and watchTowr for signs of exploitation.
  • PHP 8.6 release (November 19, 2026): The next major version of PHP is scheduled for general release.
  • End of security support for PHP 8.2 (December 31, 2026): After this date, sites still on 8.2 will stop getting fixes too.

Spotted an error? Contact the editors.