PHP2Shell Vulnerabilities Put 70% of Websites at Risk

Originally published at: PHP2Shell Vulnerabilities Put 70% of Websites at Risk - TidBITS

Although security vulnerabilities in Internet infrastructure software are generally more technical than I would cover in TidBITS, the new PHP2Shell vulnerabilities will have repercussions across the Web. Expect to see numerous websites go down or serve “Page not found” errors as they update PHP, the programming language that underpins 70% of websites. If you run a WordPress, Drupal, or Joomla site, this affects you directly.

The vulnerabilities, which have existed for more than a decade, were discovered by Wiz Research, a security firm that used Google’s Gemini 4 Argon and OpenAI’s GPT-5.6 Sol frontier AI models along with its own Wiz Atlas autonomous AI system for vulnerability research. This is just the latest example of how AI can be used to find and fix vulnerabilities, but in the wrong hands, it can also be used to exploit them. The executive summary to Wiz Research’s blog post lays it all out:

  • Wiz Research uncovered multiple critical vulnerabilities in core PHP, a popular general-purpose scripting language that powers 70% of all websites in the world. Successful exploitation could allow attackers to take control of affected servers, steal sensitive data, and deface the websites running on them.
  • PHP is a backbone of the web: it’s the programming language powering WordPress, Joomla, Drupal, Wikipedia’s MediaWiki, and many others.
  • These vulnerabilities include memory disclosure and unauthenticated remote code execution in PHP itself, independent of the application running on top of it, putting every affected website in immediate risk.
  • Every PHP version released in the last decade is affected by at least one of these vulnerabilities, going back to version 5.4. Attackers can exploit them remotely, in some cases fairly easily. Immediate patching is strongly advised.
  • On October 21, 2026, PHP released the patch fixing multiple memory-safety vulnerabilities in the core engine.
  • These findings rank among the most severe vulnerabilities discovered in PHP, and arguably in software history. The underlying flaws had been present for decades, but demonstrating their exploitability required an exceptionally complex chain of steps, at the edge of what human researchers could practically achieve. Frontier AI models substantially reduced that barrier, turning a longstanding flaw into an exploit.

Practically speaking, if you run a website, update PHP immediately or contact your hosting provider to confirm they’ve applied the patch—and pass this warning along to anyone you know who runs a site. Security experts say that exploits are already being deployed against unpatched sites.

1 Like

Just want to say this incident shows why computer security now requires a layered approach, with multiple lines of defense, even for home users. Since the PHP flaws are in up to 70% of websites, the old “I’m very careful about surfing and clicking” tactic isn’t enough on its own anymore.

3 Likes

This definitely is a serious issue.

I’m happy to see that many hosting providers (including my own) have been proactively patching their versions of PHP on shared hosting platforms, but if you are running your own web server, you need to take action ASAP. If you do have a shared hosting system, you should check to see if your provider has posted anything on its support page about the issue.

Unfortunately, I see A.I.-identified vulnerabilities like this as just another step toward making self-hosting impractical for most power users.

2 Likes

Wordfence, a third-party WordPress firewall provider, has a good, straightforward write-up describing steps that should be taken if you are responsible for a PHP-enabled website. See the “What to Do Now” section in particular.

https://www.wordfence.com/blog/2026/10/psa-php-security-updates-available-for-two-critical-vulnerabilities-update-now/

4 Likes

Thanks for that link. My hosting service (DreamHost.com) has updated PHP and I see that my WordPress site is using 8.3.36.

Now I need to turn my WordPress site back on. I modified the .htaccess file to disallow all until this was fixed.

1 Like

I also use DreamHost. I’ve been happy with them. If you’re not already running a WordPress firewall, I strongly recommend them. I’ve been using the Wordfence, but there are other reputable firewalls. Even the free version of Wordfence offers a lot of protection.

2 Likes

I have some small and basic sites with Dreamhost. I would have expected an email from them but so far nothing. Went to log in and check but the site presented was very bare bones, no the usual imagery and colors etc. Forgot I use a physical key to login so will check later.

I hope someone is asking The AI to create a fully secure replacement for html, PHP etc and a path to migrate all existing websites to the new version without any change in functionality or appearance. That imho would be a useful use of the technology. This proactive ‘white hat’ bug-finding is also useful.

1 Like

I was a little surprised that Dreamhost hadn’t sent a notice to its customers, not least because they usually are very proactive about notifying customers of upcoming upgrades and maintenance issues. They did post a status update at https://www.dreamhoststatus.com:

The official PHP security updates have been applied across the bulk of our network. Operations is currently executing final staging tests and stability checks for the remaining server groups before completing the final deployment phase.

All active threat mitigations implemented previously remain live, maintaining full coverage for your application environment. No intervention is needed on your end, and we will send out a notification upon final rollout completion.

1 Like

I’ve been a fairly minimal customer there for many years and customer communication, well, they just don’t ‘get it’. They might be technically wonderful and I tried politely to point out the, ah, room for improvement in customer communications/billing clarity but it never changed.

Recently I did have a surprisingly good response about email though.

I woulda thought, given that this event has even reached the top story in the local small town paper here in the EU, that they might have thought to send out something proactively ‘We’re on it, will let you know when it’s done, check the status of your account at…’ but no, even an event of this scale it doesn’t occur to them to notify. They still have no sense of communication. Oh well. Luckily I don’t depend on the sites and services for critical business use. Sigh.

Same here. On the other hand, there was nothing for users to do while they did the rollout of the PHP upgrades.

Except to wonder if DHost was responding, and how, or if I had to do anything myself. They could use a PR/customer communication consultant. I suppose they’re still working on it, as I still haven’t rec’d anything. Ah well.

One interesting aspect I’d be interested to read about, would be comparing this event, as it was handled by an open-source community, to how anything similar in scope and severity was handled by the tech bigs. ie informing, speed and effectiveness of response etc.

1 Like

I thought of another question on this topic, how would a web site publisher, like us little people, know if their site had fallen victim to opportunistic hackers on this? Or I suppose, on any hack. Would the host notify?

I suppose for sites with a lot of traffic and IT staff it would become evident quickly. But for small bloggers/self employed etc with no support staff other than the hosting provider, might be tricky. Then again, those sites would be less of a target in the first place. Hm.

The Atlantic has a reasonable length interview with a key player in PHP maintenance.

Not sure if the link is fully readable, but I got it all in my RSS reader.

That would depend on the nature of the hack. This particular flaw is so broad that an attacker can do pretty much anything it wants to the site. For this reason, the result of the attack can be as invisible as exfiltrating your data, or as obvious as defacing the entire site or deleting all of its contents.

Other types of vulnerability have more specific signs that can be detected by a hosting provider or malware defense system.

And don’t assume that a site’s size or the amount of traffic it receives is a metric for how likely it is to be hacked. These days it is fairly trivial to tell an LLM to write a tool that will try a list of known exploits on every web site it finds, and then do something bad when it does.

2 Likes

I’m a subscriber to the Atlantic, Here’s a gift link to the article.

4 Likes

It’s a broad subject, but I’d start with some safeguards before getting into the question of how a hosting provider might contact you.

Assume that your website(s) eventually will get hacked and act accordingly. Have a risk-adjusted backup strategy and try very hard to minimize or eliminate storing sensitive information on the server, even if authorization (passwords, etc.) is required to access it.

Your hosting provider’s responsibility will vary based on the service provided. If you are renting equipment and bandwidth for a server that you maintain, the hosting provider’s role will be relatively minimal. If you are paying for access to a managed service, like a shared WordPress server, the hosting provider will have significantly more responsibility.

Many jurisdictions place a legal obligation on hosting providers to notify clients of a breach within a fixed amount of time after the breach is discovered. If it’s a concern, you should ask about your provider’s security and notification policies before buying a service.

Since you’ve mentioned that you use WordPress, I’ll again recommend using a WordPress security/firewall plugin like Wordfence. Wordfence’s free tier offers some very helpful email notifications, which summarize attempts to login to your server, identify out-of-date themes and plugins, and identify server files that have recently changed. There are a few options to configure, but aside from giving it an email address to deliver reports to, the defaults are reasonable. Install a security plugin on every WordPress site you have.

Most hosting providers will offer various levels of active management for additional fees. Depending on your needs, they may be worthwhile.

Again, backup your hosted data on your own from time to time, even if your hosting provider takes its own backups, and carefully scrutinize your sensitive data to make sure that it is minimized or reduced.

PS. Don’t assume that having a very small website means you aren’t much of a target. Hackers may not be interested in your data, but they likely are interested in your server as a computation resource and network resource, e.g. for distributed denial of service attacks and malevolent bot activities.

3 Likes

One passage from that article resonated with me:

“There’s not enough priority and money going to properly maintain the IT infrastructure in various places…everything’s moving fast now, and it’s taking a toll on the people who are defending the stuff. At the same time, maybe this is the turning point where we actually start caring about this.”

Even in the best of times, cybersecurity is not for the faint of heart. The pressure is continuous. Attacks are attempted 24 hours a day, every day. If you work in the field long enough, some attacks will be successful. Some people thrive on that pressure. Most people, even those working as cybersecurity professionals, don’t.

Compounding the problem, infrastructure security is a low priority in many (most?) organizations. At the same time, it’s impossible to know how much is “enough.” It’s not enough to harden systems against known attacks; you have to have a plan for unknown attacks, too. That’s why most professionals place a lot of emphasis on preparing incident responses regardless of the source, i.e., how quickly can any breach be contained, how quickly can assets be validated and restored, how can losses be minimized, and so on.

Edited to fix a minor typo.

2 Likes

Thanks for the detailed reply @josehill , I’ll log in again soon and review our sites, as well as just visiting them from a browser to see if they look different. None have anything I’d consider ‘sensitive’ on them, no logins, no comments, just informational pages, email and phone contact numbers, a contact form maybe.

I think I have one small one, a few pages only, with mostly text and couple of graphics, in html and css. That one should not be in danger from this PHP event.

@david_blanchard 's earlier comment

is potentially very useful, sort of an ‘on/off switch’ for a site. With it on, I take it a 404 error page or similar would appear…

FWIW, I logged into Dreamhost via ssh and verified that the server that runs my website has been patched.

If you’re comfortable using ssh, you can login and type php -v on the command line to determine the installed version of PHP.

When you ssh into your web host you will be on a production Linux system. Feel free to look around using commands like ls, but be very careful. If you move or delete anything without being certain of what you are doing, you easily can break your site(s).

PS. For backups, there are several ways to do a full WordPress backup. All involve exporting the data from the underlying database and making an archive of the WordPress directories. You can find WordPress plugins that make that a push-button process. Once complete, use sftp to move the backup files to your local system or to a cloud storage service.

2 Likes

is potentially very useful, sort of an ‘on/off switch’ for a site. With it on, I take it a 404 error page or similar would appear…

With this particular exploit it’s important to know that disabling PHP for just your own site or even disabling access to it completely wouldn’t protect you if the appropriate PHP patch hasn’t been installed for the server that your site is on. Other applications on the server (i.e. control panel software) that depend on PHP could still be compromised and thus put the entire server at risk.

3 Likes