Critical PHP Flaws Put Business Websites at Risk—Check Yours Now
On October 21, 2026, the PHP project released emergency updates for two critical security flaws. You may never have heard of PHP, but your website probably runs on it. PHP is the programming language behind WordPress, Drupal, Joomla, Magento, and a big chunk of the rest of the Web. It runs on the server, building each page before a visitor sees it.
These flaws let an attacker run their own code on a vulnerable server without logging in first. The PHP project rates both of them 9.2 out of 10 on the industry’s standard severity scale. In plain terms, someone on the other side of the world could take over your website and anything else running on that server. The National Security Agency warned that flaws like these often give attackers a direct route to a server’s files and database, which is where customer information lives.
Updating WordPress Won’t Cover This One
Most website security problems live in a plug-in or a theme, which is why keeping WordPress updated matters so much. Researchers have nicknamed these flaws “PHP2Shell,” and they’re in PHP itself. A WordPress site with every update installed is still vulnerable if the underlying server runs an unpatched version of PHP. Fixing that is the job of whoever runs the server: usually your hosting provider, sometimes your Web developer.
The rollout was also messier than usual. Details leaked before the fix was ready, researchers have demonstrated a working attack, and Cloudflare’s chief technology officer said the company was seeing early attacks. Nobody had publicly confirmed a successful break-in by release day, but some organizations weren’t waiting to find out. BambooHR took its service offline as a precaution, and the Netherlands pulled DigiD, its government login system, along with other government sites.
Your Macs and iPhones Should Be Fine
Apple stopped including PHP with macOS 12 Monterey, and iOS never had it; there’s nothing to worry about on updated devices. However, older Apple devices could be at risk; please reach out if you have concerns. If you or a developer installed PHP on a Mac for testing (through Homebrew, for instance), be sure to update that copy too.
The Version Number Doesn’t Tell the Whole Story
The fixed releases are PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35. You’d think checking your site would just mean comparing numbers. Unfortunately, it doesn’t.
Many hosting companies run PHP packages from Linux distributions such as Ubuntu and Red Hat. Those vendors received the fixes ahead of time and often ship them under the old version number. A site that reports PHP 8.1 might be patched, and one that reports 8.3 might not be. Old versions are everywhere, too. Looking at Internet scan data from the day before the release, the security firm Mallory found that 59% of servers reported a PHP version of 8.1 or older, all versions the PHP project no longer supports.
So check the number, then keep going:
- Look up your PHP version: In WordPress, go to Tools > Site Health, click Info, and expand the Server section. Hosting control panels such as cPanel and Plesk show it too.
- Ask your host a specific question: Skip “What version are we on?” and ask, “Is the October 21 PHP security fix installed on our server, and has PHP been restarted since?” A good host can answer that quickly. If yours can’t, that’s worth knowing as well.
- Plan an upgrade from old versions: The PHP project no longer supports PHP 8.1 and earlier, and 8.2 joins that list on December 31, 2026. If your site runs any of those, schedule a move to PHP 8.3 or later. Back up the site first and test before switching the live site—older themes and plug-ins sometimes break on newer PHP, which is exactly why so many sites never got upgraded.
- Lean on Cloudflare for now: If your site’s traffic runs through Cloudflare, even on its free plan, Cloudflare has added rules that block known attack methods. That buys time. It doesn’t replace the fix.
- Watch for signs of trouble: Unfamiliar administrator accounts, files nobody added, pages that redirect to strange sites, and browser or Google warnings about your site all deserve a closer look from whoever manages it.
If You Run a Business
A website is running software and someone needs to own its upkeep. If you can’t name that person right now, start there.
Think beyond the website, too. PHP also turns up in hosting control panels and in the Web-based admin pages of some office equipment, so ask your IT provider whether anything else you rely on runs it. The NSA and the FBI’s Cyber Division both told organizations that if they can’t update right away, they should take the system offline until it’s fixed, and the UK’s National Cyber Security Centre said the same. That sounds drastic, but a website down for a day costs far less than one that’s been taken over.
The Bottom Line
Check your site today, and get a straight answer from your host about whether the fix is installed. If your site is stuck on an old version of PHP, let this be the push to finally upgrade it. If you’d like us to check your website or handle the upgrade, get in touch.
(Featured image credit: ChatGPT)
Social Media: Think keeping WordPress updated keeps your website safe? Not this time. A critical flaw in PHP, the software underneath most business websites, got an emergency fix on October 21—here’s how to make sure your site has it.