binary code over a computer chip highlighted in red
Black October & PHP2Shell: Is Your Website Safe?

Two critical PHP vulnerabilities are being exploited. Here’s how to find out if your website is exposed, who should fix it, and what to ask them this week.

In the world of cybersecurity, it would be fair to say that last week was certainly a notable one. If you haven’t been keeping up with recent news about “Black October,” here is a quick recap.

On October 21, the PHP development team released emergency updates for two critical flaws in PHP, the programming language behind roughly 7 in 10 websites whose server technology can be identified. The flaws, nicknamed PHP2Shell and tracked as CVE-2026-109618 and CVE-2026-109619, each carry a severity score of 9.2 out of 10.

In plain terms, they can let an attacker run their own code on a web server without a username or password. Wikipedia, Cummins, Signal, the Internet Archive and even government websites in several countries went offline briefly as a precaution while their teams installed the fix, not because they were under attack. A website being temporarily offline doesn’t mean it was breached.

The reality is this: If your business has a website, an online store, a customer portal or any web-based tool, this is serious enough of a threat that it is worth investigating as soon as possible.

What is Black October?

News coverage has started calling this month “Black October.” The name doesn’t refer to a single isolated incident, but to a stream of security incidents that hit all at once:

  • A compromised AI software package (LiteLLM)
  • A stolen login credential for ConnectWise Cloud Backup (formerly SkyKick), a Microsoft 365 backup tool used by many IT providers, which Huntress found being used to sign in to customers’ Microsoft 365 accounts. ConnectWise says it has found no sign that stored backups were accessed.
  • Major browsers blocking a certificate authority’s security certificates

For most small and mid-sized businesses, however, PHP2Shell is the one to check first.

Several research teams, including Wiz, Calif and OpenAI, found and reported the flaws privately to PHP’s developers over the summer. Details leaked on October 20, a day before the fixes were ready, and attackers didn’t wait. Cloudflare reported early attacks on the morning of October 21, and on October 26 the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added both flaws to its official list of actively exploited vulnerabilities. Amazon’s threat intelligence team says it recorded an exploitation attempt as early as October 17.

Why PHP2Shell is different

Most website security news is about a single plugin or app. PHP2Shell is different in four ways:

The real question: who runs your website?

Most businesses don’t run their own web server, which is exactly why issues like this slip through the cracks. The fix has to come from whoever is responsible for the server your site runs on. That’s usually one of these:

  • Your hosting provider, if your site sits on a hosting plan
  • Your web developer or agency, if they built and maintain the site
  • A software vendor, for portals, booking tools, intranets or industry apps you log into through a browser
  • Your IT provider or internal IT team, for servers they manage

Often it’s more than one. An agency may maintain the site while a hosting company runs the server underneath it. For a vulnerability as serious as this, everyone should be clear about who is applying this update.

What to do this week

  1. List everything web-facing. Start with your main website, then add the ones people forget: online store pages, customer or employee portals, old campaign or event sites, and test or staging copies of your site.
  2. Identify an owner for each page listed. If you can’t tell who’s responsible for something, that’s a problem worth solving now, not just for this incident.
  3. Ask each owner to confirm the fix in writing. Specifically: whether the system runs PHP, which version is running now, and whether it’s been updated and restarted so the fix is actually live. The fixed versions are PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35.
  4. If you’re on an older version, ask about a vendor patch. Some operating system and hosting vendors provide their own patched builds of older PHP versions. Ask whether one covers these two CVEs. It’s also time to plan an upgrade: PHP 8.2 stops receiving security fixes on December 31, 2026.
  5. If it can’t be fixed quickly, take it offline. The UK’s National Cyber Security Centre recommends this for any system that can’t be patched right away, and the FBI has urged organizations to apply the updates immediately. A few hours of downtime costs far less than a compromised server.
  6. Ask whether anyone has checked for signs of compromise. Attacks started before the fix was available. “We patched it” is a great first answer to hear, but that doesn’t mean data hasn’t been compromised.

Not sure what to say? Here’s a note you can copy and send to your host, developer or vendor:

Hi [name],

Following the PHP2Shell security advisories (CVE-2026-109618 and CVE-2026-109619), can you confirm the following for [website or system]?

  1. Does it run on PHP?
  2. Which PHP version is running now?
  3. Has the security update been applied and the service restarted?
  4. Has anyone reviewed it for unusual activity since mid-October?

Thank you,

[Your name]

Want a second set of eyes? Send us your website and we’ll check which PHP version it’s running, at no cost.

What TenHats is doing for our clients

TenHats is reviewing every system under our management where we’re responsible for the operating system or application stack, and we’re addressing affected systems as we find them.

If TenHats manages your systems, we’re already on it and will contact you if anything needs your attention.

If your organization has websites, web apps or hosting outside our management, use the checklist above with whoever runs them. If you’re not sure whether something in your environment is affected, or you don’t know who’s responsible for it, call us. We’ll help you sort it out.

The bigger picture

AI played a real role in this story, mostly on the defenders’ side. Researchers at Wiz and Calif used AI models to find and confirm flaws that had sat unnoticed in PHP for more than a decade, then worked with PHP’s developers to fix them before disclosure.

Attackers use AI too. In the ConnectWise incident, Microsoft linked the activity to a group using an AI agent framework, and Huntress found its own data consistent with that. Huntress also noted that the attack still relied on scripted tooling, and that defenders should focus on what an attack does, not how fast it moves. For PHP2Shell, the wave of early attacks followed the October 20 leak of the vulnerability details.

Speed has clearly changed. CrowdStrike found that most exploitation of flaws with public exploit code now happens within 48 hours of that code’s release. You can’t control that pace, but you can control how quickly you respond. That comes down to three things:

  1. Knowing what you have
  2. Knowing who owns it
  3. Having someone who will actually pick up the phone and apply the fix.

Businesses with those three things in place had a busy week this month but caught the risk quickly. If you don’t have those yet, this is a good time to start, and we can help.

Need help securing your website? Talk to the TenHats team at 865-770-5920 or contact us online. We’ll help you find out where you stand.

Experience the Difference

Reach out today to talk to a strategic technology advisor. We look forward to partnering with you.