The PHP and AI security issue, explained in plain English
What the PHP security alert means, where AI fits in, and how we’ve been working with our suppliers to help keep customers’ websites safer.
If you’ve seen the recent headlines about PHP, AI and website security, you might be wondering what on earth it all means for your business.
Fair question. Most people want their website to work. They don’t want a crash course in the software underneath it.
We’ve been working with our hosting and software suppliers, checking the advice and carrying out the necessary compatibility work and PHP upgrades. The aim is to keep our customers as safe as we can, while making sure their websites still do the jobs they need to do.
Here’s what has happened, in normal language.
Think of your website as a shop. The pages people see are the shopfront. Behind it, there’s equipment doing the work: finding information, putting pages together and processing requests.
PHP is one of the tools used behind the scenes. It runs on the computer hosting the website, usually called a server. Depending on how a site is built, PHP might help display products, process a form or manage a customer’s basket.
You don’t normally see it, and you don’t need to install it on your own laptop to visit a website. It is part of the website’s working machinery.
That’s why a PHP update can matter even when the design hasn’t changed at all.
A simplified picture: your browser asks for a page, the server does the work, and stored information helps it build the response. PHP can be part of that middle step.
On 21 October 2026, the PHP project released urgent fixes for two serious weaknesses. Under certain conditions, an attacker could use them to run instructions on a vulnerable server without first logging in.
In everyday terms, there was a fault in the machinery behind the shopfront. Someone with the right knowledge could potentially interfere with it from outside. The details depend on how the server and website are set up, but the advice to apply the fixes is clear. PHP’s official announcement.
This is why a website looking normal doesn’t answer the security question. A homepage loading tells you that the homepage loads. It doesn’t tell you whether the software underneath has received the necessary fix.
Equally, an alert about a weakness isn’t proof that a particular website has been broken into. A vulnerability means there is a route that needs closing. Establishing whether anyone has used it is a separate investigation.
AI was involved in the research. People used AI tools to help investigate weaknesses, work out how they could be exploited and check the proposed repairs. The PHP Foundation explains that people still make the decisions and work on the patches. The Foundation’s explanation.
So the headline doesn’t mean your website suddenly has an AI feature that needs switching off. The problem is in PHP itself. AI helped researchers understand the risk and develop the response.
I’d think of it as giving an experienced mechanic better diagnostic equipment. It can help them find a difficult fault, but somebody still has to understand the result and check the repair.
The useful takeaway for a business owner is quite straightforward: keep up with maintenance and take genuine security notices seriously. You shouldn’t need to become an AI expert to get your website looked after.
We’ve worked with our suppliers to understand which protections they have applied and what still needs doing at website level. That distinction matters. The hosting company looks after the server environment; the website’s own software, theme and extensions need attention too.
Our work has included checking PHP versions, reviewing supplier patch information, preparing backups, testing older website code against newer PHP, and carrying out upgrades after those checks.
Some older code needed compatibility repairs before it would work properly with the newer version. Those changes were tested in a private copy before being put onto the live website. We also checked the working parts afterwards, including product pages, baskets and checkout screens where relevant.
It’s practical work that customers may never notice on the front of the site. That’s rather the point. A security update needs to protect the business without leaving an important part of the website broken.
Backup, speak to the supplier, test the changes and keep checking. These illustrations show the approach in simple terms; they aren’t screenshots of a customer’s systems.
Sometimes an update is straightforward. Sometimes an older theme or extra feature relies on behaviour that a newer PHP version has changed.
Imagine replacing a piece of equipment in your shop. The new one might be better, but you still need to know it fits the connections and works with everything around it. Websites have similar dependencies.
That’s why we check compatibility, keep a recovery route and test the parts people actually use. Seeing the homepage is a start. Checking a contact form, a login or a basket gives you a much more useful picture.
Testing needs to move promptly alongside the security response. An incompatible theme is something to resolve, not a reason to leave a known weakness indefinitely.
The releases issued for this alert were PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12, covering the supported branches available at the time. These are the October fixes, not a promise that those exact versions will remain the latest. PHP release details.
Some hosting suppliers also apply a security repair to an older software package without changing the headline version number you see. This is called a backport. We’ve checked supplier confirmation of this as part of our review; an old-looking number on its own doesn’t settle whether that specific fix is present.
It doesn’t mean old software can stay in place forever, either. PHP versions have support deadlines, and moving to a supported version remains part of the longer-term work. PHP’s support timetable.
It addresses these PHP weaknesses when the correct fix is properly applied. There are other things to look after as well.
The content management system is the part you use to edit the website. That needs updates of its own. So do add-on features. Administrator accounts, passwords, file uploads and backups all need sensible attention.
A firewall can help filter unwanted traffic, but it doesn’t replace the PHP repair. Google’s published response makes that distinction clear: extra protection can reduce exposure while the underlying software is being fixed. Technical guidance on the response.
I wouldn’t tell you any website is completely risk-free. What we can do is take notices seriously, work with the right suppliers, check what has actually been done and keep the remaining work moving.
If we look after your website and you’re unsure about something you’ve read, give us a call. We can explain what applies to your setup, what has been checked and whether there’s anything you need to do.
If you manage your own hosting, ask whoever maintains it to confirm that the October PHP fixes are applied to the version actually serving your website. Don’t assume a general “updates enabled” message covers everything, and don’t change versions at random if you’re unsure what the site needs.
Keep using strong, unique passwords and two-step sign-in wherever it’s available. If a page behaves strangely, a login appears that you don’t recognise or you receive an unexpected security message, let your website support team know promptly. Don’t share passwords in an email asking for help.
For our customers in Huddersfield and further afield, the message is simple: we’ve been working with our suppliers to help keep your websites as safe as we can. We’ll explain the technical bits without expecting you to know all the terminology.
Got a question about PHP, the AI headlines or your website? Give us a call on 07815 121999. We’re happy to talk it through.
Information relates to the October 2026 PHP security release. Illustrations created for this article using AI; they show general concepts, not real customer systems.