Western Slope Digital Logo+16235658445
← All Resources

Black October and Your Business Website

What to check this week, what to ask your host, and how to decide between patching your site and rebuilding it.

Last updated: October 27, 2026

If you own a business website, you may have seen the phrase “Black October” this month. It is not one attack. It is a nickname for a cluster of serious security disclosures, most of them published in the week of October 19, 2026. Several affect software that runs a large share of the web.

Most of the list matters to software teams: a GitLab flaw, a poisoned release of an AI developer library, and a certificate authority whose keys turned out to be weak. For a small business website, two items matter. One affects almost every WordPress site until its host patches PHP. The other affects the newer, JavaScript-based sites, including the ones we build.

PHP2Shell: the one that matters for WordPress sites

WordPress, Drupal, and Joomla are written in PHP. On October 21, the PHP project shipped emergency fixes for two flaws, CVE-2026-109618 and CVE-2026-109619, now known together as PHP2Shell. Both are rated critical. Together they can let an attacker run their own code on your web server without logging in. The researchers who found them demonstrated exactly that against WordPress, Drupal, and Joomla.

Three details matter for business owners:

  • The flaws are in PHP, not WordPress. Updating WordPress, your theme, or your plugins does not fix this. The fix is a PHP update on the server, and on most hosting plans only your host can do it.
  • Attackers did not wait for the patch. Technical details leaked hours before the fix was released, and security firms reported exploitation attempts before the fix was out. Exploit code is now public.
  • Old PHP gets no fix. The fixed versions are 8.2.35, 8.3.36, 8.4.27, and 8.5.12. PHP 8.1 and older no longer get updates from the PHP project. Internet scans published after the disclosure found that most PHP servers that show their version run one of those unsupported versions. PHP 8.2 also stops getting security fixes on December 31, 2026.

Node.js: modern sites were not immune

The same day, Node.js shipped fixes for ten flaws. The most serious, CVE-2026-111497, is in the Brotli decoder that Node.js bundles. Brotli is a compression format. An app that decompresses Brotli data from an attacker can crash, leak memory, or in the worst case run the attacker's code. The fixed versions are 22.23.4, 24.22.1, and 26.12.1. Node.js 20 has reached end of life and gets no fix.

Node.js runs Next.js, the framework we use, so we are not going to tell you a modern stack makes you immune. It does not. What it changes is how big the target is and who has to act. We explain that below.

What to do this week

  1. Find out what your site runs on. If it is WordPress, log in and go to Tools, then Site Health, then the Info tab. The Server section shows your PHP version.
  2. Ask your host, in writing. Ask whether your site is on PHP 8.2.35, 8.3.36, 8.4.27, 8.5.12 or later, or on a vendor build with the fixes for both CVEs. Ask whether PHP was restarted after the update. A server can show the new version in one place and keep running the old code until it is restarted.
  3. If you are on PHP 8.1 or older, plan a move now. Upgrading PHP on an old site can break an outdated theme or plugin. This is often the point where patching stops being simple.
  4. Update WordPress, your theme, and your plugins anyway. Delete plugins you no longer use. This does not fix PHP2Shell, but it closes the other doors.
  5. Look for signs of a break-in. Check for admin users you did not create, pages you did not publish showing up in Google, and visitors being sent to other sites. If you find any, change every password connected to the site and get help before you restore anything.
  6. Make sure you have a backup from before October 20. Store it somewhere other than the web server.
  7. If your site runs on Node.js, confirm it is on 22.23.4, 24.22.1, 26.12.1, or a platform runtime that includes the fix, and redeploy it.

Patch or rebuild?

You do not need a new website because of Black October. If your host has patched PHP, your plugins are actively maintained, and someone is responsible for keeping it all updated, patching is the right call.

A rebuild starts to make more sense when:

  • The site is stuck on an old PHP version because the theme or a plugin breaks on a newer one.
  • It depends on plugins that no longer get updates.
  • Nobody is clearly responsible for updates, so they happen only after something goes wrong.
  • You keep paying for fixes, and the site is also slow or hard to edit.

If two or more of those are true, the next emergency patch will bring the same scramble. At that point, it is worth pricing a rebuild against another year of emergency fixes.

How a modern site shrinks the target

A typical WordPress site builds every page on request. Each visit runs PHP, your theme, and every active plugin, and the login page sits at an address every attacker knows. PHP2Shell worked because there is always PHP code running that an attacker can reach.

The sites we build work differently. Most pages are built ahead of time and served as finished files, so a visit to your homepage runs very little code. There is no plugin directory to keep current and no public admin login. Contact forms and other dynamic features still run code on the server, which is why the Node.js flaw still mattered.

What was different in October was who had to act. On Vercel, for example, the platform rolled out patched Node.js runtimes and added firewall rules for both flaws. The site owner's part was a redeploy, plus a version change for sites still on Node.js 20. On our plans, that part is ours too.

How Western Slope Digital can help

We are a web design and SEO agency in Grand Junction, and we work with businesses across the Western Slope. There are three ways we can help, depending on where your site is now.

  • Free check. Send us your site address. We will tell you what it runs on, whether it looks exposed, and what to ask your host, so you can decide what to do next.
  • Keep it secure. Our website plans include hosting, security, SSL, backups, and three content edits a month, starting at $0 down and $99 a month. Keeping the platform current is part of what you pay for, not a separate bill when the next flaw is announced.
  • Rebuild on a modern stack. If your current site is stuck on old software, we can rebuild it as a fast, modern site. A rebuild is quoted up front, since the cost depends on the size of the site and what it needs to do. Because we also do SEO, we map your old page addresses to the new ones with redirects, so you keep the search rankings you have already earned.

Get a Free Website Security Check

Tell us your website address and who hosts it. We will look at what it runs on and tell you, in plain English, whether you need to act.

Sources

Black October FAQs

What is Black October?

It is a nickname for a cluster of serious security disclosures in October 2026, not a single attack. For small business websites, the two that matter are PHP2Shell, a pair of flaws in the PHP language that runs WordPress, and a flaw in the Brotli decoder bundled with Node.js.

Is my WordPress site affected by PHP2Shell?

If your PHP version is not at least 8.2.35, 8.3.36, 8.4.27, or 8.5.12 on its branch, and your host has not applied a backported fix, assume yes. You can see your PHP version in WordPress under Tools, then Site Health, then the Info tab, in the Server section. Your host can confirm whether a fix has been applied.

Will updating my WordPress plugins fix it?

No. PHP2Shell is a flaw in PHP itself, not in WordPress or its plugins. The fix is a PHP update on the server, which on most hosting plans only your host can do. Keep WordPress and plugins updated anyway, but do not treat that as the fix for this.

Do I need a new website?

Not necessarily. If your host has patched PHP, your plugins are maintained, and someone keeps it all updated, patching is enough. A rebuild makes sense when the site is stuck on an old PHP version, depends on abandoned plugins, or nobody is responsible for keeping it updated.

Are modern sites built with Next.js immune?

No. Node.js, which runs Next.js, had its own serious flaw in the same week. The difference is the size of the target and who has to act. Pages that are built ahead of time have far less code running on each visit, and on a managed hosting platform the platform patches the runtime and adds firewall rules. The site still needs to be redeployed, which on our plans is our job.