Swan LogicLet’s talk

Security & maintenance

PHP2Shell didn’t affect my client websites. Here’s what I checked anyway.

A critical PHP security flaw made headlines in October 2026. My clients’ sites don’t run PHP, but I audited the whole server anyway, and found something else that needed fixing.

In late October, a pair of serious security flaws in PHP hit the news. If you run a website, there’s a fair chance you heard about it, or got an email from your web host about it.

PHP is the programming language behind a huge share of the web, including WordPress. The two flaws, nicknamed PHP2Shell (officially CVE-2026-109618 and CVE-2026-109619), were rated critical. In the wrong conditions they let an attacker run their own code on a web server without logging in. Details leaked online on 20 October, before the fixes were ready. The PHP team released patched versions the next day, and attackers were already trying their luck.

So the first thing I did was check whether any of my clients’ websites were exposed.

Was I affected?

No. The websites and systems I build and host don’t run on PHP, and PHP isn’t installed on the server. That particular flaw had nothing to attack.

I could have stopped there. But “that specific problem doesn’t apply to me” isn’t the same as “everything is fine”. A scare like this is a good prompt to check the whole thing, not just the one item in the headlines.

What I checked

This wasn’t a penetration test or a forensic investigation. It was a practical, end-to-end check of the things that actually keep a website running safely:

  • What’s exposed to the internet. The firewall blocks everything by default and only lets through what needs to be public. Databases only accept connections from inside the server.
  • Who can log in, and how. Server access is locked to security keys. Password logins and direct admin logins are switched off.
  • Updates. I reviewed every pending operating system update and applied them.
  • Security certificates. These are what put the padlock in your browser and keep visitors’ data encrypted.
  • Backups. I didn’t just confirm backups exist. I checked they’re current, stored away from the server, and that restoring them actually works. A backup you’ve never restored is a hope, not a plan.
  • Recovery. I rebooted the whole server on purpose, to prove every website and app comes back on its own without anyone restarting things by hand.

What I actually found

Most of it was in good shape. But one thing wasn’t.

On one client’s site, the security certificate was failing to renew. The site was still working, because the existing certificate hadn’t expired yet. But a redirect rule in the server configuration was quietly blocking the automatic renewal check. Left alone, that site would eventually have shown visitors a “your connection is not private” warning. That’s the kind of thing that makes customers close the tab.

The fix was small: adjust the redirect so the renewal check could get through. The certificate renewed straight away and is now valid well into next year.

That problem had nothing to do with PHP. I only found it because I went looking at everything.

Updating carefully, not blindly

When I applied the server updates, I deliberately held one back: an update to Node.js, the software several of my client applications run on.

Not because it was risky in itself, but because changing the thing your apps depend on, at the same time as everything else, makes it hard to know what broke if something does. So the operating system updates went in first and were verified. The Node.js update gets its own planned window, tested against the apps that use it.

It’s a bit slower. It’s also how you avoid turning maintenance into an outage.

What this means for your business

If your website runs on WordPress or anything else built on PHP, check with whoever hosts it that they’ve updated to a patched version of PHP (8.5.12, 8.4.27, 8.3.36 or 8.2.35, or newer). Don’t assume it’s happened automatically.

And whatever your site runs on, it’s worth asking whoever looks after it three simple questions:

  1. Do we have backups, and when did you last test restoring one?
  2. Who applies updates, and how often?
  3. Would anyone notice before our security certificate expired?

If the answers are vague, that’s worth knowing now rather than on the day something goes wrong.

Building a website is only part of the job. Knowing how to maintain it, and how to recover it, matters just as much.


Further reading: the PHP project’s security release notes, Huntress’s rapid-response write-up, and Datadog Security Labs’ technical analysis.

Zac Swan, founder of Swan Logic, laughing in a sunny backyard in Waimate

About the author

Zac Swan

I build websites and business systems around how established New Zealand businesses actually work.

zac@swanlogic.co.nz

There’s probably a better way to do that.

Let’s find it.

You’ve probably already got something in mind. Free 30-minute chat, no obligation.Projects typically start from $6,000.

Tell me what’s not working