The short answer
On October 21, 2026, PHP and Node.js both shipped emergency security updates. The PHP flaws (nicknamed PHP2Shell) let an attacker take over a server without logging in. The Node.js flaw (Node2Shell) can do the same to apps that handle compressed data.
If your website runs on PHP, which includes every WordPress site, you need PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35 or newer. If you run anything on Node.js, you need 26.12.1, 24.22.1 or 22.23.4 or newer. Anything older than PHP 8.2 or Node 22 has no official fix at all.
It was a busy week
Most weeks I build websites. Last week I mostly answered the phone.
It started with a warning from the NSA. Not to me personally. To everyone. Their cyber team posted a warning telling every organization using PHP to get ready for an emergency patch, and to take their site offline if they couldn't update right away.
The NSA does not usually tell small businesses to unplug their websites. So people noticed.
Within a day, hosting companies like HostGator were sending their own version of that warning to millions of customers. Update PHP immediately. Contact your developer. Act now.
The problem is a lot of those customers don't have a developer. Or they have one who wasn't answering.
What actually happened, in plain English
Two separate problems landed on the same day. Neither one was caused by anything a website owner did.
PHP2Shell (CVE-2026-109618 and CVE-2026-109619). PHP is the language that builds the page on the server before it reaches your browser. It runs roughly 70% of the websites on the internet, including every WordPress site. Researchers found two flaws in how PHP handles oversized requests. A specially crafted request could let a stranger run their own code on your server, no password needed. Both flaws scored 9.2 out of 10 for severity.
The PHP team gave one day of notice on October 20 and released the fix on October 21. Government agencies in the US, UK, Canada, Australia and the EU all told site owners to patch or go offline. Some European governments actually pulled their own sites down that day.
Node2Shell (CVE-2026-111497). Node.js powers a lot of modern websites and web apps. It also builds many sites that look simple on the surface. On the same day, Node.js fixed ten vulnerabilities. The worst was in the code that unpacks Brotli-compressed data, a common way to shrink files sent over the web. Feed it bad data and an attacker could crash the app, read its memory, or take it over. CISA added it to its list of actively exploited vulnerabilities on October 27.
One detail made this week feel different. Both PHP flaws were found with help from AI. That cuts both ways. AI is also very good at reading a patch and working backward to an attack. One researcher put it bluntly: updates now have to go in almost instantly.
Which versions are safe
| Software | Version line | Safe version (or newer) |
|---|---|---|
| PHP | 8.5 | 8.5.12 |
| PHP | 8.4 | 8.4.27 |
| PHP | 8.3 | 8.3.36 |
| PHP | 8.2 | 8.2.35 (support ends December 31, 2026) |
| PHP | 8.1, 8.0, 7.x | No official release. Upgrade. |
| Node.js | 26 | 26.12.1 |
| Node.js | 24 | 24.22.1 |
| Node.js | 22 | 22.23.4 |
| Node.js | 20, 23, 25 | End of life. No fix. Upgrade. |
That "no fix" row is the scary one. Cisco estimated roughly half of the PHP installs facing the internet were too old to receive the patch at all.
What I did for my clients
The first thing I did was boring. That is the point.
I went through every site I manage and checked three things. Which version of PHP or Node.js it was actually running. Whether that version had a patch. And whether the patch was really in place, not just available.
That last part trips people up. Some hosts install the fix but keep showing the old version number, because they patch the existing release instead of moving to a new one. Some update PHP on the server but leave your site pinned to an older version in the control panel. Some do nothing until you ask. You have to look.
For the WordPress sites, that meant confirming the PHP version per site and per host. For the sites built and deployed with Node.js, it meant checking the runtime on the build and hosting side, not just the code in the project.
Every Matchlight client was patched within 24 hours of the vulnerabilities going public. None of them had to call me first. Most of them never knew there was a problem, which is exactly how it should feel.
Then the phone started ringing
The rest of the week belonged to people who were not my clients.
Some had built their own site on WordPress years ago and hadn't logged into the host since. Some had a developer who built the site and moved on. Some had a team they were paying every month who simply wasn't responding.
They all had the same email from their host. It said update PHP immediately. It did not say how. It did not say what version they were on, or whether they were even affected.
One business owner forwarded me the NSA post with a simple question: did you check this when you audited our sites? Their current provider was still working on an answer. They wanted one now.
The other common move is to find the PHP version switch in the hosting control panel and flip it. On an older site with an outdated theme or plugins, that one click can patch the hole and break the website at the same time.
Nobody who called me was careless. They were doing exactly what the email told them to do. The email just assumed they knew things they had no reason to know.
Most of them needed the same thing first. A calm, fast answer about where they actually stood, and a plan for what to do next. Once they had that, the panic went away.
How to check if your website is affected
You can do most of this yourself in about fifteen minutes.
- Figure out what your site runs on. WordPress, Joomla, Drupal, WooCommerce and most cPanel hosting run on PHP. Sites built with Next.js, Astro, Nuxt or a custom web app usually involve Node.js somewhere. Squarespace, Wix and Shopify handle their own servers, so this one was on them, not you.
- Find your PHP version. In WordPress, go to Tools, then Site Health, then the Info tab, and open the Server section. In cPanel, look for "MultiPHP Manager" or "Select PHP Version." Check every domain, not just the main one.
- Compare it to the safe list above. On PHP 8.2 through 8.5 with a version at or above the safe number, you are patched. On 8.1 or older, you are not, and no official patch is coming.
- If the number looks old, ask your host one direct question. "Is my server patched for CVE-2026-109618 and CVE-2026-109619?" Some hosts patch the existing version without changing the number you see. A yes or no answer in writing settles it.
- Check Node.js where it runs. That might be your server, your hosting platform's build settings, or a developer's machine that builds and deploys your site. You need 22.23.4, 24.22.1 or 26.12.1 or newer.
- Back up before you change anything. Switching PHP versions on an older site can break themes and plugins. Take a full backup, then test on a staging copy if your host offers one.
- If you couldn't patch quickly, look for signs of trouble. Unknown admin users, files you didn't upload, or unexpected redirects are reasons to get help now. The UK's cyber agency recommended checking for backdoors on any system that stayed exposed.
If any of those steps made you nervous, that is useful information too.
What a developer is actually for now
AI tools can build a decent website in an afternoon. I use them every day and I tell business owners to use them too. So it is fair to ask what you are paying a developer for.
This week answered that question better than I could.
The value was not writing code. Nobody needed new code. The value was three things.
Knowing what to check. The host's email said "update PHP." It did not say that your site might be pinned to an old version, that the number on screen might lie, or that the switch might break your theme. Knowing where the traps are comes from having stepped in them before.
Being current before the alarm goes off. The safest sites last week were the ones already on a supported version. Upgrading from PHP 8.3 to a patched 8.3 is a five-minute job. Upgrading from PHP 7.4 under pressure is a weekend. Staying current is cheap. Catching up is not.
Answering fast. When government agencies tell people to unplug their websites, "we'll look into it next week" is not an answer. The people who called me weren't asking for a miracle. They wanted someone to pick up the phone, tell them where they stood, and handle it.
That is the job now. Less building from scratch. More knowing what matters, in what order, and being there when it counts.
Frequently asked questions
What is PHP2Shell?
PHP2Shell is the nickname for two critical PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619, disclosed on October 21, 2026. They let an attacker run code on a web server without logging in. Both are rated 9.2 out of 10 for severity.
Which PHP versions fix PHP2Shell?
PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 fix both vulnerabilities. Any newer release on those branches is also safe. PHP 8.1 and older have no official fixed release.
What is Node2Shell?
Node2Shell is CVE-2026-111497, a critical flaw in the Brotli decompression code bundled with Node.js. It can let an attacker take over an app that decompresses data they control. Node.js 22.23.4, 24.22.1 and 26.12.1 fix it.
Is my WordPress site affected by the PHP vulnerability?
Every WordPress site runs on PHP, so it depends on your PHP version. Check Tools, then Site Health, then Info, then Server in your WordPress dashboard. If the version is below the safe list, or older than 8.2, update or ask your host to confirm the patch.
My host emailed me to update PHP. What should I do?
Find your current PHP version, back up your site, then ask your host whether your server is patched for CVE-2026-109618 and CVE-2026-109619. If you need to switch PHP versions, test on a staging copy first. Older themes and plugins can break on newer PHP.
Do Squarespace, Wix or Shopify sites need to do anything?
No action is needed on the site owner's part for these platforms' own servers. They manage their infrastructure directly. Custom apps or separate servers connected to those sites should still be checked.
Should I take my website offline?
The NSA and other agencies advised taking a site offline only if it cannot be updated quickly. For most small business sites on a reputable host, confirming the patch is the faster and better path.
If you're not sure where you stand
This won't be the last week like this. AI is finding old bugs faster than ever, and the patches will keep coming.
If you run your own site, keep going. Seriously. Just know who you'd call when the next email shows up.
And if you got that email last week and still aren't sure what happened, reach out. I'll tell you where you stand, plainly, and help you sort out what to do next. No panic required.
Work with Matt
If your site hasn't had a real checkup in a while, the diagnostic is a flat $997 and covers your full digital presence, including the stuff under the hood.
Start the Diagnostic →Sources
- PHP security advisory and release notes, php.net
- NSA Advisory: PHP Updates
- Critical PHP vulnerabilities expose most websites to potential compromise, Cybersecurity Dive
- Node.js Brotli decoder bug could allow remote code execution, The Hacker News
- Inside Node2Shell: CVE-2026-111497, Akamai
- Node.js October 2026 security releases advisory, Konfirmity
