If your business has a website, there's a security update released today that's worth a quick email to whoever looks after it. You don't need to understand the technical side, and you shouldn't try to fix it yourself. Here's the short version.
On October 21, the team behind PHP released emergency updates for two critical vulnerabilities, tracked as CVE-2026-109618 and CVE-2026-109619. Both are rated 9.2 out of 10. In plain terms, an attacker may be able to run their own commands on a vulnerable web server without needing a username or password. That doesn't mean every website running PHP has been hacked. It does mean the servers behind those sites should be updated soon.
You may have no idea whether your website even uses PHP, and that's completely normal. It runs quietly behind the scenes on a huge number of sites, including WordPress, Drupal, and Joomla, as well as plenty of custom-built ones. Most business owners never have to think about it. This week is an exception.
A normal WordPress update may not fix this
If you use WordPress, you're probably used to updating WordPress itself, your plugins, and your theme. This is different. The flaw is in PHP, which runs on the server hosting your website, so clicking "Update All" in your dashboard doesn't necessarily touch it. The fix has to happen at the server level.
The PHP team released patched versions today: 8.5.12, 8.4.27, 8.3.36, and 8.2.35. Hosting companies and server administrators should be installing those, or the equivalent fixes from their operating system vendor. Older versions of PHP need extra attention, since some are no longer supported by the PHP project at all. You don't need to memorize any of those numbers. What matters is that whoever manages your website knows about this and has dealt with it.
Is anyone actually attacking this yet?
Reports are mixed, so here's what we know. The details leaked about a day before the planned release, which is why the patches came out early. Since then, Cloudflare and the security firm watchTowr have both said they're seeing early attack attempts, while the PHP team itself has not confirmed that. Other security companies say they haven't seen attacks in their own data, and what's being reported is mostly probing. The UK's national cybersecurity agency told organizations to update immediately. So the sensible reading is that attackers are interested and you shouldn't wait to find out, but it doesn't mean your site has been compromised.
What should you do?
Contact whoever hosts or manages your website and ask whether your server has been patched. You don't need to install anything or work out which version of PHP you're running. If you're not sure what to say, you can send them this:
Hi, I saw that critical PHP security updates were released on October 21 for CVE-2026-109618 and CVE-2026-109619. Can you confirm whether our website uses PHP and, if so, whether the server has been patched to address these vulnerabilities?
A good hosting provider can answer that in a sentence or two. If the reply is vague, or "we're looking into it" with no date, ask again. If your site doesn't use PHP, this issue likely doesn't apply to you. And don't assume everything is fine just because your site still loads normally. Security flaws like this rarely cause visible problems.
A note from Pine State Sites
The sites we host and manage don't run on PHP, so this doesn't affect our customers' hosting. We're still sharing it because it's the kind of thing website owners should hear about when it happens, whoever their provider is.
If your website is hosted somewhere else, contact your current provider first. They know your setup and can tell you what needs updating. If you're not sure who manages your hosting, your site was built years ago and the original developer is long gone, or you can't get a clear answer, get in touch with us. We can help you work out what your site is running and whether this update is something you need to act on.
Today is just one of those days.