PHP’s Critical Vulnerability - What WordPress Site Owners and Agencies Need to Do Today

  • Ryan Anderson

  • 5 min read

  • 1024 words

An illustration of PHP being attacked

Updated October 22, 1:15 PM GMT-6

To say this week has been a storm of tech issues and cybersecurity woes would be an understatement. Both PHP and Node.js, two of the most widely used pieces of software on the world wide web, reported some serious security flaws.

For PHP, the flaws let an attacker run their own code on your server without the need to log in. That’s about as serious as it gets in cybersecurity. It’s like having your neighbours coming into your home whenever they please, changing all the clocks, and swapping out your cereal for flax seeds.

For Node.js, a tool developers use to build and run modern web apps, ten vulnerabilities were recently patched on October 21, four of them high severity.

Why it matters to you

You might be thinking, “I’ll just update my website. I’ve been holding off on the last WordPress update for a while, and now seems like as good a time as any to pull the trigger on it.”

But the problem isn’t your website’s content, theme, or plugins. Those are just the blocks with which your home is built. The real problem is in the basement, in the concrete foundation that was poured long before you put up curtains or chose a colour scheme.

That means pushing updates on WordPress or Drupal won’t protect you here. Someone has to go in, clear out the cobwebs, and update the underlying software on the server.

How do you know you’re affected?

Do you run WordPress, WooCommerce, Drupal, Joomla, or another PHP system? Then yeah, you’re probably affected. If you’re on something like Shopify, Squarespace, or Wix, those platforms manage their own servers, so patching is their job. Check their status pages or announcements.

Likewise, if you’re on a static setup and your front end is served via a CDN, this flaw can’t reach it. However, a headless setup with a PHP backend will still need patching.

When in doubt, ask your developer.

Don’t have a developer? You’ll need to go in and find out which software you’re using and which version of PHP or Node.js you’re currently running.

What happens if you do nothing?

It’s impossible to predict individual risk. So the answer is: maybe nothing? Now, I really can’t make that question mark big enough at the end there, because different sites attract different traffic. What happens to some might never happen to you.

As of the morning of October 22, security firms are reporting active attempts to exploit these flaws, some of them starting before the patch was even released. No one has publicly confirmed a major compromise yet, but you shouldn’t wait for one.

We all have that one relative who, despite repeated warnings, likes to open emails they shouldn’t and click on links. Sometimes nothing happens. Sometimes they lose all their data and are left scratching their heads wondering what they did wrong.

Don’t be that person. The longer a known flaw stays unpatched, the more likely someone finds it. A successful attack could mean stolen customer data, spam or malware planted on your site, a defaced homepage, or a Google warning that tanks your traffic and destroys your SEO.

What do you need to do?

Five things you should actively be doing right now.

  1. Ask your host or developer to confirm if you’re on an affected PHP version and to update it immediately. The fixed versions as of this posting are 8.5.12, 8.4.27, 8.3.36, and 8.2.35.
  2. If you’re on PHP 8.1 or older, there’s no official patched release, so ask whether your host has backported one, and plan an upgrade.
  3. Make sure there’s a fresh backup first, and test, test, test the site afterward. I can’t stress this enough: TEST! Older plugins have a tendency to break on newer PHP.
  4. For Node.js, have your dev update to 26.12.1, 24.22.1, or 22.23.4, including any build service. Again, these are the known updates as of this posting, so make sure to check back as this develops.
  5. Ask as well to check for unfamiliar admin accounts or files.

If you’re handling things yourself, you’ll need to do a few things differently.

  1. First, find your PHP version. In WordPress, go to Tools > Site Health > Info > Server. Your host’s control panel (cPanel, Plesk, or a custom dashboard) usually has a place to check your PHP version as well.
  2. Once found, compare it to the fixed versions (8.5.12, 8.4.27, 8.3.36 and 8.2.35). Some hosts patch the underlying server without changing the version number, so if the number looks old, ask your host’s support if it’s patched rather than assuming.
  3. If you’re on 8.1 or older, there’s no official patched release. You’ll need to ask your host about a backport and plan an upgrade immediately.
  4. Back up your site first, then switch PHP versions in your host’s panel. If you have a staging site, now would be a good time to utilize it before pushing it live.
  5. Check the site afterward. Click through pages, test your forms, order something from the shop, everything a normal customer would do. Older plugins are notoriously finicky when it comes to new PHP updates, so test, test, test.
  6. If your site is built or run with Node.js, update to 26.12.1, 24.22.1, or 22.23.4, and check your build service’s settings.
  7. DO NOT RELY ON FIREWALL PROTECTION TO SAVE YOU. Firewalls are great at adding an extra layer of protection, but PHP has said itself there’s no complete mitigation and upgrading is the only safe response.

It’s crazy out there right now, and so many developers and users are scrambling for news and information. If you manage a site, take a look around. Check for modified files in the last few days, especially in the uploads folder, and review server logs for strange requests.

If anything looks wrong, change your password, turn on two-factor authentication, and bring in a professional cleanup crew.

Stay safe out there everyone.

Note: this is still developing, so check PHP’s and Node.js’s official advisories and your host’s notices for updates.