If you caught the tech headlines in late October (or maybe you got an email from me about it), you may have seen words like “critical,” “emergency patch,” and “70% of the internet” flying around. That kind of language can make any business owner wonder whether their website is in trouble. The short answer: if your site is on a host that applied the fix, you are probably in good shape – but it’s worth checking just in case. The longer answer is worth a few minutes of your time, because understanding what happened makes it much easier to keep your site safe going forward.

Here is a plain-English walkthrough of what happened, what it meant for WordPress websites, and the simple habits that protect your site from this kind of issue.

What Actually Happened

On October 21, 2026, the team that maintains PHP released emergency updates to fix two serious security flaws. Security researchers nicknamed them “PHP2Shell,” and they were rated critical, scoring 9.2 out of 10 on the standard severity scale.

The important thing to understand is that the news was about a discovery and a fix. A weakness was found, and the people who maintain PHP released a repair for it. The headlines did not mean that websites everywhere had been hacked, and they did not mean your site had been broken into.

That said, it is fair to be honest about what followed. Once a weakness like this becomes public, people with bad intentions start looking for servers that have not been updated yet. Within about a week, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) confirmed that attackers were actively targeting unpatched servers. That is exactly why web hosts and website managers moved so quickly. A site that got the fix early was protected. A site left on an unpatched server was the kind of target attackers were hunting for.

So What Is PHP, Anyway?

PHP is a programming language that runs behind the scenes on the server that hosts your website. You never see it, but it does a lot of heavy lifting. Every time someone visits a page, fills out a contact form, or books an appointment on your site, PHP is doing the work of building that page and handling that information.

PHP is not just a WordPress thing. It powers an estimated 70% of websites on the internet, including sites built on WordPress, Drupal, Joomla, Magento, and many custom-built applications. So when a flaw shows up in PHP itself, it affects a huge portion of the web all at once, which is why this story made the news far beyond the tech world.

A helpful way to picture it: if your WordPress site is a house, PHP is the foundation and wiring underneath it. You can have a beautifully decorated house with great locks on the doors, but if there is a problem in the wiring, it needs to be fixed at the foundation level.

What This Meant for WordPress Websites

In practical terms, these flaws could have allowed an attacker to run their own code on a website’s server without even needing to log in. That is what made them so serious. Someone who gains that kind of access can potentially install malware, redirect your visitors to sketchy websites, use your site to send spam, or get at information stored on the server.

Here is the part that surprised a lot of WordPress owners: updating WordPress, your theme, or your plugins does not fix this. The problem lived in PHP, which sits underneath WordPress on the server. WordPress itself did not need an update. The fix had to be installed by whoever manages the server, which is usually your web host.

A couple of other details are worth knowing:

  • Your dashboard may not tell you. Many hosts applied the fix without changing the PHP version number you see in WordPress, so a version number alone does not always confirm whether the patch is in place.
  • Older PHP versions were left out. The official fixes were released for PHP 8.2, 8.3, 8.4, and 8.5. Sites still running PHP 8.1 or older did not get an official fix, which makes upgrading those sites a priority.
  • PHP 8.2 is nearing retirement. PHP 8.2 reaches its end of life in December 2026, meaning it will stop receiving security updates. If your site is on 8.2, now is a good time to plan a move to a newer version.

How Hosts and Website Managers Responded

When the fix was released, web hosts and website managers got to work right away. Most of the major WordPress hosts patched their servers quickly, which meant many site owners were protected before they even heard about the issue.

As for my own response: as soon as I became aware of the issue, I checked every website I host and manage. That meant confirming which version of PHP each site was running, verifying with each host that the fix had been applied, and updating sites wherever an update was needed. This is a big part of what ongoing website care looks like. Most of the time it is quiet, behind-the-scenes work, and then a moment like this comes along and it really counts.

How to Check Whether Your Site Is Protected

If you manage your own website, here are two simple steps you can take today:

  1. Ask your web host directly. Send a quick support message asking: “Has the PHP2Shell security fix (CVE-2026-109618 and CVE-2026-109619) been applied to my server?” A good host will give you a clear yes or no.
  2. Check your PHP version. In your WordPress dashboard, go to Tools > Site Health > Info, then open the Server section. If your PHP version starts with 8.1, 8.0, 7, or anything lower, talk with your host or developer about upgrading.

If you have someone who manages your website for you, it is perfectly reasonable to ask them what they did in response. They should be able to tell you.

Everyday Habits That Keep Your Website Safe

Events like this are a good reminder that website security is not a one-time task. The good news is that the habits that protect you are straightforward, and most of them take very little time once they are in place.

Keep All of Your Software Updated

This includes WordPress itself, your plugins, your theme, and the PHP version running on your server. Updates often include security repairs, and the longer software goes without them, the more exposed it becomes. While you are at it, delete any plugins or themes you are not using. Inactive software can still be a weak spot. The same general rule applies to other devices – your phone, laptop, computer, etc. Keeping their software updated helps keep you secure from similar vulnerabilities.

Use Strong, Unique Passwords

Every account connected to your website should have its own password: your WordPress login, your hosting account, your domain registrar, and your email. Reusing one password across several accounts means a single leak can open several doors. A password manager such as Roboform or Bitwarden makes this easy by creating and remembering long, random passwords for you.

Change Passwords Periodically

Changing your passwords after a security event like this one is a smart move, especially for your hosting account and any WordPress administrator accounts. It is also a good idea to review your passwords on a regular schedule, update any that are weak or reused, and change them right away if a service you use reports a data breach.

Turn On Multi-Factor Authentication

Multi-factor authentication (sometimes called two-factor authentication or 2FA) adds a second step to logging in, usually a code from an app on your phone. Even if someone gets your password, they cannot get in without that second step. Turn it on for your WordPress login, your hosting account, and your email. It is one of the most effective protections available, and it only takes a few minutes to set up.

Limit Who Has Administrator Access

Every administrator account is another key to your website. Review your user list from time to time and remove anyone who no longer needs access, like a former assistant or a past contractor. Give people the lowest level of access they need to do their job.

Keep Reliable Backups

Backups are your safety net. If something ever does go wrong, a recent backup can get your site back online quickly. Make sure your backups run automatically, are stored somewhere separate from your website’s server, and have actually been tested so you know they work.

Know Who Is Responsible for What

Many business owners assume their host handles everything, or that their web designer does. Take a moment to confirm who is responsible for updates, server-level security, backups, and monitoring. When everyone knows their role, issues like this one get handled quickly instead of falling through the cracks.

The Bottom Line

The PHP2Shell news was a serious security issue, and it was handled the way these things should be: the problem was found, a fix was released, and hosts and website managers moved quickly to apply it. If your site is on a well-maintained server, you are very likely already protected.

Your website is one of your most important business tools. A little regular care keeps it secure, fast, and working for you, so you can stay focused on serving your clients.

Not sure whether your site was patched, or would rather have someone keep an eye on these things for you? Reach out today and I will be happy to take a look.