Highlight of the day: yet another WordPress site left to rot since 2024.
I had pointed out the problem months ago, but the client had simply replied with a "thank you."
Today, an employee emails me saying he "wanted to install some updates, but PHP isn't up to date," followed by a whole explanation of how PHP should be updated. Systemd was involved, obviously.
Spoiler: PHP was already up to date, running the latest 8.3 release, inside a dedicated FreeBSD jail for that client's website.
I take a look, and the site is compromised. WordPress 6.6.x. I immediately tell them to contact the web agency responsible for maintaining it, otherwise I'll have to take the site offline.
Shortly afterwards, they reply that the web agency says *I'm* supposed to handle it.
I've never touched that website, apart from providing the hosting. It's full of completely unnecessary plugins, and it's basically just a brochure website.
I inform the client. I wait.
The client is desperate. He asks me, "Please, help us. Our reputation is at stake."
That's when I have one of my five-minute bursts of fury.
I clone the entire site into a static version using an old plugin that still worked (something I had developed years ago with another developer). I make a few adjustments and show it to the client.
"Thank you."
From today onwards, static only for those kinds of sites. And whenever they need changes, they'll ask me.
In today's world, we simply cannot afford to compromise on security anymore, even if that means coming across as overly strict or categorical.