Brainfarts of an Idle Mind

Was it the right choice to take the websites offline?

Charles McCrimmon 3 min read

Having local councils and health boards take their websites offline due to this vulnerability can be unsettling, but it was a sensible precaution to take; the National Cyber Security Centre’s (National Cyber Security Centre, 2026) advice is and was to update immediately, apply temporary mitigations if you can’t and consider taking the systems offline if neither can be done quickly. So a few hours of planned disruption with these sites offline is far better than a compromised system taking them offline for weeks, as we saw in the retail attacks on M&S and the Co-Op last year, and putting residents’ or patients’ data at risk

What makes this noteworthy and higher profile than most other vulnerabilties is how the risk itself changed: the underlying weakness in PHP, which runs a large share of the web, was first spotted in 2024, No one could show that it could be exploited in any real way, so it wasn’t treated with any urgency. This year, in about a 2 week window, (Tzadik et al., 2026) researchers using advanced AI tools such as Wiz Atlas, Gemini 4 Argon and ChatGPT-5.6 Sol showed real-life working examples of how this could be turned into a working attack. Several teams discovered this independently around the same time, so something previously unfeasible to exploit became practical overnight, and Amazon Threat Intelligence (Moses, 2026) identified the attack method being attempted on Oct 17th 2026.

Should people be concerned about these websites being taken offline in the short term? No, not about the sites going offline; it’s not the public’s responsibility to fix these issues, but those who run the websites and services, and the councils and NHS board teams, have acted correctly overnight and taken the sites offline until fixes can be installed. My bigger concern would be the smaller organisations, local businesses, charities and community groups running sites that are not actively maintained. Amazon are now reporting that the issue is being broadly exploited, so any site that hasn’t been updated is at real risk. Many of these groups will not even realise they use PHP because it’s built into products and platforms that they rely on.

Will we see more of this? Absolutely. As these tools become more powerful and more people learn to use them, we will see far more vulnerability reports. The PHP team (The PHP Foundation, 2026) has already said that, because of AI tools, they are seeing far more reports than before, and because attackers have access to the same tools, or similar ones, they are benefiting from the same leaps and bounds in knowledge as defenders.

This case itself shows how fragile the process is. This was, in part, a partial leak and an early release of a demonstration video, which cut the time that developers and organisations had to prepare and deploy the fixes before it became general knowledge. This means the gap between a system flaw becoming public and attackers trying to exploit it is now measured in hours. The NCSC (National Cyber Security Centre, 2026) advice is clear, and we’ve seen that, in these situations, a short-term system outage is a more secure approach than leaving the vulnerable system online and exposed to exploitation.

Where this has been used

References

How to cite this piece

McCrimmon, C. (2026) 'Was it the right choice to take the websites offline?', Brainfarts of an Idle Mind, 17 November. Available at: https://mccrimmon.me/was-it-the-right-choice-to-take-the-websites-offline/ (Accessed: 17 November 2026).

Leave a Reply

Your email address will not be published. Required fields are marked *