Skip to content
WP Hack FixEst. 2005

Security news

PHP has fixed two critical flaws: make sure your host updates today

Updated · Disclosed October 20, 2026 · By Adam Taylor

Updated October 28: These flaws are now being used in attacks, and the US Cybersecurity and Infrastructure Security Agency (CISA) has added both to its list of vulnerabilities known to be exploited. Working attack code is public. If your host hasn’t confirmed you’re on a fixed version yet, chase them today. The details are under “Is anyone using it?” below.

Updated October 21: The fix is out. When we first published this on October 20, PHP had only announced it was coming, and the details were still rumour. PHP has now released the fixed versions and confirmed the worst of what researchers were reporting. This post has been rewritten to match.

This isn’t about a plugin, and it isn’t about WordPress itself. It’s about PHP, the programming language WordPress is written in, which runs on your hosting server underneath everything else. Like the libheif problem last month, no WordPress update will fix it. PHP has to be updated on the server, which usually means your host.

PHP has released fixes for two critical flaws, both rated 9.2 out of 10, and is urging everyone to update immediately. The fixed versions are:

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

What the flaws let an attacker do

Both let a stranger run their own code on your server, without logging in. That’s the worst kind of flaw there is: once someone can run code, they can add admin accounts, plant backdoors, read your database, or use your server to attack other sites.

They’re two separate bugs (CVE-2026-109618 and CVE-2026-109619) in how PHP tidies up after handling a web request. A carefully crafted request can leave PHP’s internal bookkeeping in a broken state, and an attacker can turn that into running code.

PHP considers the risk highest on servers using Apache with mod_php, a common older setup. There, PHP’s own security team has demonstrated a working attack that triggers before WordPress even loads. That matters: security plugins run inside WordPress, so on those servers they can’t see this attack, let alone stop it.

Am I affected?

Almost certainly, until your host updates. PHP says every PHP installation that serves web pages is at risk, which covers every common hosting setup (PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP, and LiteSpeed). Every WordPress site runs on one of those.

To find your version, log in and go to Tools → Site Health → Info, then open the Server section.

  • 8.5.12, 8.4.27, 8.3.36, or 8.2.35 or later: you’re on a fixed version.
  • Anything lower on 8.2 to 8.5: you’re not patched yet. Ask your host when they’re updating.
  • PHP 8.1 or older: PHP itself no longer releases updates for these versions. Some hosts and Linux vendors patch older versions themselves, so ask yours directly whether they’ve applied a fix. If they haven’t, ask to be moved to a supported version.

One catch: some hosts get PHP from their Linux vendor, who patches the existing version without changing the version number. So an “old” number isn’t proof you’re unpatched, and only your host can tell you for certain. Asking is quicker than guessing.

On PHP 8.2? It’s fixed today, but PHP stops supporting 8.2 on December 31, 2026. After that, no more fixes. Plan to move to a newer version before the end of the year.

Is anyone using it?

Yes. Amazon’s security team saw a first attack attempt on October 17, four days before PHP released the fix, and more from several different attackers on the day of release. Cloudflare reported early attacks the same day.

By October 24, a researcher had watched attackers take over test servers running an unpatched PHP 8.4 with Apache mod_php, the setup PHP warned was most at risk. Security firm Trail of Bits has since confirmed that publicly available attack code works against unpatched PHP 8.2 through 8.5. On October 26, CISA added both flaws to its list of vulnerabilities known to be exploited.

Nobody has published a count of real sites taken over, and not every attempt will succeed on every server. But the attack code is out, it works, and it’s being used. An unpatched server should now be treated as a target.

What to do now

  1. Check your PHP version using the steps above.
  2. If your host manages PHP (most shared and managed hosting), contact them or check their status page, and ask them to confirm you’re on a fixed version, or that their vendor’s patch has been applied.
  3. If you run your own server, take a backup, then install the updated PHP packages from your Linux distribution or vendor. PHP says those vendors got the fixes in advance, so they should be available already. If you get PHP from the remirepo repository, check it for updated packages too.
  4. If your host can’t update today, PHP’s advisory lists some temporary settings that reduce the risk. They’re partial and technical, and PHP is clear that only the update is a real fix. Point your host or developer to PHP’s advisory if they need them.
  5. On PHP 8.1 or older, use this as the push to move. Take a backup first and check the site afterwards. Older plugins and themes sometimes break on a newer PHP.

On a Protect plan? Our updates cover WordPress, plugins, and themes, but PHP itself is your host’s to update, so it’s worth confirming with them today too.

If you’re not sure where your site stands, or you’re stuck on an old PHP version, talk to us.

Worried your site's already been hit?

If something looks wrong, we'll check it and clean it up. If we can't fix it, you don't pay.

We reply within 1 business day (Mon–Fri, 9–5 ET)