Skip to main content
Altivus

Cybersecurity

Your Website Runs on Software You’ve Never Heard Of. This Week, It Needed an Emergency Fix.

By Kyle Maulden · October 29, 2026

Laptop showing a business website with a padlock, server rack behind it.

Most business owners think about their website in terms of what customers see: the homepage, the contact form, maybe an online store. Very few think about the software underneath it. This week, that hidden layer became the most urgent security issue on the internet.

On October 21, the team that maintains PHP announced fixes for two critical security flaws. PHP is the programming language that quietly runs most of the web. According to W3Techs, it runs about 69% of the websites whose server-side language is known (November 2026), including every WordPress site and WooCommerce store. The flaws allow an attacker to take control of the web server behind a site, in some cases without needing a password. Working attack code is already public, and the news coverage has started calling it “Black October.”

If your business has a website, there is a good chance this applies to you. Here is what it means and what to do, in plain terms.

Why this PHP vulnerability is different

Website security problems usually live in plugins or themes, the add-ons that give a site its features. Those get fixed when you click “update” in your website dashboard. This problem is one level deeper. Updating WordPress, plugins, or themes does not fix it. The PHP software on the server itself has to be updated, and that is usually your web host’s job, not something you can do from your dashboard.

There is also a reason this is moving so fast. According to CNBC’s reporting, researchers used advanced AI models to find these flaws. The same kind of tools make it easier for criminals to find and attack unpatched sites at scale. Former CISA Director Chris Krebs told CNBC that smaller companies should scan for weaknesses constantly, patch as fast as possible, or take outdated systems offline. We wrote about this broader shift in what AI-powered cyberattacks mean for business, and this week is a clear example of it.

What’s actually at risk for your business website

It is tempting to think, “It’s just our brochure website. There’s nothing on it worth stealing.” That is rarely true. A compromised website can:

  • Quietly redirect your visitors to scam pages, using your name and reputation.
  • Capture whatever people type into your forms, including contact details and, for online stores, payment information.
  • Expose passwords, login tokens, and connection keys stored on the server, which can lead attackers into other systems like your email marketing or payment accounts.
  • Get your domain flagged by Google or email providers, which can hurt your search ranking and cause your business emails to land in spam.

For businesses with online stores or customer portals, the stakes are higher, because the server holds keys that connect to payment providers and customer data.

Four things to do this week

1. Find out who is responsible for your website’s server. This sounds basic, but it is often the hardest part. Many businesses had a site built years ago by a freelancer or agency and never revisited who maintains it. You need a name: your hosting company, your web developer, or your IT provider.

2. Ask one specific question. Don’t settle for “We’re on it.” Ask your host or developer: “Which version of PHP is running our site, and does it include the fixes for CVE-2026-109618 and CVE-2026-109619?” Those two codes are the official identifiers for this week’s flaws. A good provider will answer quickly and clearly. If you run WordPress, you can also see the version yourself under Tools, then Site Health, then the Info tab. Be aware that the “good” status there checks only the general version, not whether this specific fix is applied, so confirm with your provider.

3. If your site is on an old version, treat it as urgent. PHP versions older than 8.2 no longer receive security fixes at all. WordPress’s official guidance, echoing national cybersecurity agencies, says that if you manage your own server on one of those versions, you should consider taking the site offline until it is updated. A few days without a website is far cheaper than cleaning up after a breach.

4. If you take payments online, plan to change your keys. If your store ran on an unpatched server, ask your provider to rotate (replace) the payment and connection keys after the update. It is a small step that closes the door even if something was taken.

The bigger lesson

This week is a reminder that your business depends on layers of technology you never see, and each layer needs an owner. Your website, your email, your backups, and the software running underneath them all need someone whose job it is to notice when an emergency fix comes out and apply it quickly.

That is not a question of buying more tools. It is a question of knowing who is watching. If you are not sure who that is for your website today, that is the gap to close first. And if something does look wrong, our guide to the first hour of a cyberattack walks through what to do.

If you’d like a second set of eyes, Altivus can check which version your site is running, confirm the fix with your host, and help you put a clear owner in place for the layers underneath. Get in touch and we’ll help directly.

Filed under Cybersecurity

A practical next step

Ready to discuss your situation?

Bring the question you are trying to answer. We can start with the business need and clarify the appropriate next step.

Office address
151 FM-407
Suite 200
Argyle, TX 76226

Fields marked are required.

What can we help with?

A short business explanation is enough. Please don’t include passwords or confidential records.

We use these details to respond to you. See our Privacy Policy.