Most business owners couldn’t tell you which version of PHP their website uses, and honestly, why would they? It’s plumbing. Nobody thinks about plumbing until the basement floods.
The basement flooded on October 20. Somebody posted details of two serious PHP bugs online before the people who maintain PHP had a fix ready to ship. They’d been planning a tidy, coordinated announcement for a day or two later. Instead, hackers got the blueprint early, and by the 21st researchers could already see attacks hitting live servers.
WordPress runs on PHP. If your business site is a WordPress site (and odds are decent that it is), this one was aimed at you whether you read the headlines or not. What happened next depended a lot on who hosts your site.
A Plain Look at PHP2Shell
The two bugs go by CVE-2026-109618 and CVE-2026-109619, though the security crowd has been calling them PHP2Shell. Both got a 9.2 severity rating out of a possible 10.
Here’s what bothers security people most about them. A hacker doesn’t need your login. There’s no password to guess and no phishing email involved. They fire off a specially shaped request at an unpatched server, and that server will run whatever code they hand it. After that, your site is basically theirs to mess with. Some attackers plant malware. Others scoop up whatever customers type into your forms, or bury spam links in your pages where you’ll never see them, or bounce your visitors to some sketchy site selling knockoff sneakers.
Under the hood it gets complicated fast. One flaw shows up when PHP runs short on memory partway through handling a visitor’s request. The other has to do with scraps of data that PHP should throw away after each request but occasionally hangs onto. You really don’t need the details to get the gist, which is that a total stranger could end up controlling the computer your website runs on.
Oddly, these bugs weren’t new to the people who found them. Researchers turned them up in August, with an assist from AI tools, and everyone had kept quiet while a fix was prepared. The leak forced PHP’s hand. Patched versions (8.5.12, 8.4.27, 8.3.36 and 8.2.35) went out on October 21.
Bigger Than the Usual Plugin Panic
WordPress security news tends to follow a pattern. Some plugin has a hole, everyone checks whether they have it installed, and most people don’t, so life goes on.
PHP2Shell broke that pattern because there was no plugin to check. PHP is the layer below WordPress, below WooCommerce, below your theme and every add-on you’ve ever installed. Something like 70 percent of websites with an identifiable server language run on it. Versions as old as PHP 5.4, which is more than ten years old at this point, were affected.
Even the way a server was configured didn’t matter much. The PHP team’s own guidance said any setup that serves web traffic was at risk, from PHP-FPM to Apache with mod_php to LiteSpeed.
Nobody had to wonder whether hackers would bother. The security firm watchTowr saw exploitation happening on October 21, the very day the fixes came out, and CISA added both bugs to its list of actively exploited vulnerabilities on October 26.
Running Old PHP? You’re on Your Own
Here’s where it gets ugly for a lot of small businesses. The PHP project only patched versions it still supports, so 8.2 and newer. If a site is on 8.1, 8.0, 7.4 or something even older, there’s no official fix and there won’t be one.
It’s more common than you’d think. Plenty of sites were built years ago and never touched again at the server level. Others had an upgrade attempt go sideways (a plugin broke, a page went blank) and the developer rolled it back and moved on. That made sense in the moment. Now those same sites are running software with a famous, actively exploited hole in it.
A Third Bug Joined the Party
As if two weren’t enough, PHP disclosed another remote code execution flaw on October 23, CVE-2026-115560. This one lives in a feature called session upload progress. Because it only affects sites set up in an unusual way, PHP considers it lower risk and plans to fix it in a regular release rather than another emergency update.
The October 21 patches don’t touch this one. In the meantime, the recommended fix is to turn off session upload progress on the server. A decent host can flip that setting in a few minutes. A rock-bottom host might not get around to it at all.
Where Budget Hosting Falls Apart
Right after a vulnerability like this goes public, automated bots start sweeping the internet for servers that haven’t been updated. Those first few days are when the real damage happens, and during that window, your safety mostly comes down to how quickly your host reacts.
Inexpensive shared hosting plans have a built-in problem here, and it isn’t laziness. Cheap hosting makes money by cramming as many websites as possible onto each server while spending as little as possible on support. When something urgent comes up, patches roll out on the host’s schedule, which on a giant shared network can stretch into days. A lot of the customers on those plans are also parked on old PHP, the very versions that aren’t getting fixed. With hundreds of sites sharing one machine, a single hacked account can become everybody’s problem. Malware scanning tends to cost extra. So does cleanup, if they offer it.
Calling support doesn’t always help either. Don’t be surprised if the answer is “go update PHP yourself,” with zero interest in whether your site will still work afterward.
That bargain plan looks a lot less appealing once a hack sinks your search rankings or Chrome starts flashing a red warning screen at your customers. Throw in a data leak and you’re having a very bad month. Professional cleanup alone can easily cost more than several years of solid hosting.
Octiv Digital Hosting Clients Never Felt It
Sites hosted by Octiv Digital came through PHP2Shell without a scratch. Zero were affected.
That’s not luck. Every hosted client site runs on managed cloud servers, and they all get the same strong security measures, with no stripped-down tier for smaller accounts. Security updates get handled at the server level, so clients don’t have to patch PHP or even know what version they’re on. Advanced malware scanning runs on every site and flags files or code that look off. PHP versions and server settings get monitored over time, which keeps sites from sliding onto outdated software without anyone noticing. The people testing updates are the same ones who do WordPress maintenance on those sites, so they actually know what a given client’s site is supposed to look like.
When PHP2Shell hit the news, Octiv Digital clients didn’t have to lift a finger. No support tickets, no scrambling.
Checking a Site Hosted Somewhere Else
If your site lives with another host, block off 15 minutes today and go through this.
- Find your PHP version under Tools, then Site Health, then Info, then Server in your WordPress dashboard.
- You want to see 8.5.12, 8.4.27, 8.3.36 or 8.2.35, or a later patched build from your host. Seeing 8.1 or lower means you need to act fast.
- Contact your host and ask straight out whether they’ve patched CVE-2026-109618 and CVE-2026-109619, when they did it, and how they’re handling the session upload progress issue.
- Run a malware scan if your server sat unpatched at any point after October 20. Keep an eye out for admin users you don’t recognize, files you never uploaded, odd redirects and spam pages turning up in Google.
- Double check that you’ve got a clean, recent backup stored somewhere other than that server.
Watch how your host answers. Fuzzy answers, or silence, tell you plenty about how the next crisis will go.
How to Tell if a Site Has Been Hit
A hacked website doesn’t always look hacked, at least not to the person who owns it. Often the first clue comes from someone else. A customer mentions a bizarre pop-up. Google Search Console starts listing pages you didn’t create. Sometimes visitors land on completely unrelated sites, or the site drags for no obvious reason, or your host sends an email about unusual resource usage. A brand new admin account in WordPress that nobody remembers setting up is a big red flag.
If any of that sounds familiar, don’t wait. Get the site professionally cleaned, change every password, and consider a move to a more secure host.
Looking Ahead
PHP2Shell won’t be the last of these. AI tools are helping researchers find serious bugs faster than before, and attackers can use those same tools, so the gap between a bug going public and the first wave of attacks keeps getting shorter. Sticking to web security best practices isn’t optional anymore.
Think about everything your website does for your business. It brings in leads, answers questions at midnight, and makes a first impression long before anybody picks up the phone. Hosting probably deserves more attention than it gets. Cheap hosting tends to get expensive the moment something breaks.
Let Octiv Digital Take a Look
Wondering how your current host would have handled PHP2Shell? Octiv Digital can help you find out. The team will look over your setup, check your PHP version and security, and move your site to fully managed hosting with malware scanning and proactive server updates included.
Reach out to Octiv Digital today to book a hosting review. The next big vulnerability doesn’t have to keep you up at night.









