Michael O'Brien ยท

PHP 5 to 8.4 in one evening, because the work was done before the news

Last month a critical PHP security announcement went out in the middle of a workday. By that evening, a local nonprofit's WordPress site had moved from PHP 5 to 8.4.27, and the members never saw it go down.

PHP is the language WordPress runs on, and it sits underneath every plugin and theme on the site. The nonprofit's site was still on PHP 5, a version that stopped getting security fixes years ago. Upgrading it had been on the list for a long time and wasn't urgent, until it was.

What happened

Most of the credit goes to the members. One had flagged the old PHP version a while before, and we had already talked through the options, which is the only reason the evening wasn't a fire drill. Another member texted me about the announcement, which I had missed during the workday. A third had already staged a new server on PHP 8.

My part was the last step. I backed up the member data, switched the site to the new server, upgraded further to the recommended 8.4.27, and relaunched. It took about an hour.

What it avoided

Without the staged server, the site would have been down for twelve to twenty-four hours, with outage reports from members and no clear answer about whether their data was safe. We also skipped sending an all-member email that would have raised more questions than it answered. I looked through the site afterward and found no sign that it had been targeted.

Why PHP 5 was still running

The site worked. A visitor never sees the PHP version, the host keeps serving the old one until someone asks for the new one, and an upgrade can break a plugin that hasn't kept up. So the upgrade waits for a quiet week, and a security announcement doesn't wait for one. That's the same position as a company of thirty people whose website belongs to the marketing director or the operations lead, and whose contractor finished the build three years ago.

What changed afterward

  • The server keeps PHP current on its own, so the site won't fall years behind again.
  • Plugins update automatically.
  • Unused plugins and themes are gone, because a plugin that is switched off still sits on the server where it can be attacked.

Three questions for your own site

What PHP version does it run? In WordPress it's under Tools, then Site Health, then Info, and your host's dashboard shows it too. Anything below 8.2 no longer gets security fixes, and as of November 2026, 8.2 stops getting them at the end of the year.

Who has an admin login to the site, the host, and the domain? If the list includes a contractor who finished or someone who has left, those logins come off first.

When did someone last restore a backup? Restore one to a copy of the site this month, and time how long it takes.

If those take longer than ten minutes to answer, the website security check answers them and makes the updates on a safe copy first. If you think someone is already in, the account security cleanup is the place to start, because an update can erase the evidence of how they got in. The longer argument for doing this now is in the deferred maintenance on your website just came due.

Next step

Which of the three questions couldn't you answer?

Bring that one to a 30-minute call, with the web address. You'll leave with a short list of who should still have access.