You may have seen headlines this week about two separate security problems affecting the internet — one involving a company called Cloudflare, one involving PHP (a piece of software a huge number of websites are built on). Neither story is really about any one organisation specifically, but because they're getting a lot of coverage — and because two big stories landing in the same week is a bit unusual — here's a plain-English summary: what happened, who's fixing it, and what, if anything, it means for you.
What actually happened, in plain terms
1. A "trust certificate" problem. Every secure website (the little padlock icon in your browser) relies on behind-the-scenes certificates that prove a site is really who it says it is — a bit like an ID card for a website. This week, it came out that some of those certificates — issued by a company called eMudhra — weren't as secure as they should have been. In theory, someone could have used this weakness to create a fake "ID" for a website and impersonate it convincingly. To be clear, this isn't a crack in the encryption that protects your data as it travels across the internet — that part remains sound. It's a weakness in the "checking someone's ID" step that happens before the connection is even made. Cloudflare and other big internet providers found it and fixed it on their end within about 24 hours, mostly before the public had even heard about it.
2. A software flaw in PHP. PHP is used to run a huge share of websites worldwide. Security researchers found two serious flaws in it this week. In plain terms: under specific, deliberately engineered conditions, someone could send a website a carefully crafted request designed to confuse how PHP manages its own memory, and potentially use that to run their own code on the server or see data they shouldn't — without needing a password or login. Because PHP is so widely used, this made headlines. What's reassuring is how it was handled: the PHP team quietly gave advance warning two weeks ago that a major fix was coming, and companies like Cloudflare had protective measures in place before the public announcement, so a lot of websites were shielded automatically.
Is this affecting you?
We're not aware of anything about either story directly affecting us or anything we manage. The organisations responsible for the affected software and infrastructure responded quickly, and this kind of rapid, coordinated fix is a normal part of how the internet handles these things — it's not a sign that something has gone especially wrong. That said, nobody can give a 100% guarantee for every system everywhere, which is exactly why the next section matters more than the technical detail above.
If you run any website built on PHP, or work with someone who manages one for you, it's worth a simple question to whoever runs that hosting: has the underlying PHP software been updated, not just whatever's built on top of it? The two are separate, and updating one doesn't automatically update the other.
What to watch out for
You don't need to manage servers or websites, and you don't need to patch, update, or fix anything yourself for either of these stories — that part is being handled centrally by the people responsible. But there are a few simple things worth keeping in mind this week:
- Big security stories like this are prime time for scam emails and texts. It's common for scammers to send fake "your account was affected, click here to secure it" messages riding on real news like this. Be a little extra cautious this week with anything that asks you to click a link or enter your details urgently — even if it looks official.
- If something feels off, say something — don't try to fix it yourself. An unexpected password-reset email, a strange warning message in your browser, a website behaving oddly, or anything that just doesn't feel right: it's always worth reporting rather than ignoring it or trying to sort it out yourself. You're not expected to diagnose it or know whether it's serious — that's what reporting it is for.
- If you manage a website built on PHP, or work with someone who does, it's worth checking directly whether this has been patched, rather than assuming routine maintenance has covered it.
Our approach
Stories like these come up fairly regularly, and most of the time they're resolved by big infrastructure providers before the average person ever needs to act. We keep an eye on things like this so you don't have to — checking what's actually affected, applying fixes promptly where it's on us to do so, and treating it as routine rather than an emergency. We just wanted to be upfront about what's in the news this week, and honest about what we do and don't know, rather than letting you find out secondhand or overselling how certain we can be. No need for alarm — just the usual bit of extra awareness.
Questions, or something you want to flag? Just ask.