AI Is Finding Security Flaws Faster. Your Website Has to Keep Up.
Published · Sebastian
On 21 October, people in the Netherlands found they could not log in to DigiD, the login they use for government services. Nobody had attacked it. It had been switched off on purpose, along with government websites in Finland and France, a Danish school platform and a long list of others, because a serious flaw in PHP was about to be made public and taking a site offline was safer than leaving it exposed.
PHP is the programming language behind most of the web, every WordPress site included, and behind every site we build. The flaw was found with the help of artificial intelligence. Four weeks later, critical fixes for three of the most widely used pieces of web software arrived within two days of each other. This article is about what changed, what it means for an ordinary business website, and why every site we build now comes with a care plan.
What happened in October
Two flaws in PHP, which security researchers nicknamed “PHP2Shell”, let an attacker run their own code on a web server without logging in to anything. Every version of PHP going back to 5.4, released in 2012, was affected by at least one of them. PHP rated both 9.2 out of 10 for severity and said plainly that there was no complete workaround: updating was the only safe choice.
PHP gave a day’s notice and released the fixes on 21 October. That notice is what led so many organisations to switch their sites off rather than wait, and they were right to be cautious. Cloudflare reported attack attempts before the fixes were even published, and millions of them by the following day.
The part AI played
The flaws were found in August, independently, by two teams that were both working with AI models. A researcher at the security firm Calif used OpenAI’s GPT-5.6 Sol, and the researchers at Wiz used Google’s Gemini and OpenAI’s models alongside their own tools. According to Kaspersky, the AI helped them analyse PHP’s source code, show that an attack would actually work, and test the fixes. Both reported the flaws to PHP privately, which is how it should work.
October was not a one-off. Google’s threat intelligence team counted 5,045 vulnerabilities disclosed in January 2026 and 10,740 in August: the monthly number doubled in eight months. Not all of that is down to AI, and most new disclosures are minor. But Google’s early data suggests the flaws AI finds skew towards the serious kind: half of them let an attacker run code remotely, against about a quarter of the rest. Google itself calls that an early indicator rather than an established trend, and it is worth reading it that way.
None of this means AI is making the web less safe on its own. The same tools help the people writing the fixes. What has changed is the pace. Serious fixes now arrive more often, and once a fix is published, attackers can study it to work out what it repairs. The window between “a fix exists” and “somebody is trying it on your server” is short. In October, the attacks started before the fix was even out.
18 and 19 November: three critical releases in two days
- nginx, 18 November. nginx is the web server that sits in front of a large share of the world’s websites, including the ones we host. Five critical flaws, nicknamed “nginx2root”, were fixed in versions 1.31.9 and 1.30.7, each rated 9.2 out of 10.
- WordPress 7.1.5, 18 November. A security release fixing 18 flaws, the worst of which could let somebody without an account take control of a site.
- PHP, 19 November. PHP warned the day before that the highest severity was critical. The releases for every supported version fixed 18 vulnerabilities, seven of them rated critical by the security firm Patchstack.
To be clear about where these stand: at the time of writing, none of the November flaws is known to be under attack. That is exactly the moment to update, before it turns into another October.
What this means for a small business website
A website is software running on a server, and software is never finished. Every release like the ones above is a gap that opens on the day it is announced and closes only when somebody applies the fix. A site that was built, launched and then left alone falls a little further behind with every one of them.
It is tempting to think a small site is not worth attacking. It does not work like that. These flaws are exploited by automated tools that try every server they can reach, and they are after the server, not your content. A five-page site for a joiner in Penrith runs on the same PHP and the same kind of web server as an online shop, and a server taken over through it can be used to send spam, host scam pages or attack other sites. Not having a database or taking payments does not change that.
So the useful question is not whether your site is a target. It is this: when the next October arrives, is somebody watching, and can they apply the fix that day?
Why every site we build now comes with a care plan
This is why we changed how we work. Every site we build now comes with a care plan, and we don’t host websites without one. Under a care plan, security updates are applied as they are released, the site and the server are monitored, and there is one scheduled upgrade a year to keep everything on a supported version.
Here is how that worked this autumn. On 21 October, every site we host was updated on the day PHP released its fixes, and none of them had to go offline. On 18 and 19 November, the nginx and PHP fixes went on to our servers the day each one came out. Our sites don’t run WordPress, so that release did not apply.
The reason it was routine rather than a rescue is that each update was small. The sites were already current, so moving to the next release was one short step, not a leap across years of missed updates. It is the same as servicing a car regularly instead of waiting for it to break down, and it is a large part of why a build costs less when it comes with a care plan.
Common questions
Was my website affected by the October PHP flaws?
If your website runs on PHP, which includes every WordPress site, it was exposed until the server was updated. The fixes came out on 21 October in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Versions 7.4 to 8.1 are past their end of life and got only source code patches, with no ready-made releases, and older versions got nothing. Ask whoever looks after your hosting which PHP version the site runs and when it was last updated.
Does a simple website with no database or payments still need updates?
Yes. The October flaws let an attacker run their own code on the server itself, whatever the website does. A brochure site with five pages runs on the same PHP and the same web server as an online shop, and a server taken over through it can be used to send spam, host scams or attack other sites.
How quickly are updates applied under a care plan?
Security updates are applied as they are released. In October and November 2026, every site we host was updated on the day each fix came out, and none had to be taken offline. One larger scheduled upgrade a year keeps the underlying software on a supported version.
Is AI making websites less safe?
Not by itself. The same tools that help researchers find flaws also help them confirm and fix them, and the October flaws were reported to PHP before they were made public. What has changed is the pace: serious fixes arrive more often, and attackers move quickly once a fix is published. A website is only as safe as the speed at which those fixes reach it.
If you are not sure about your own site
Ask whoever looks after it two questions: which version of PHP does it run, and when was it last updated? If the answer to either is “I’m not sure”, that is worth fixing before the next release, not after it. If you would like us to take a look, or you are planning a new site and want it looked after from the day it launches, get in touch through the contact form.
Sources
- PHP news archive: the October advisory, the 18 November notice and the 19 November releases
- Kaspersky: websites taken offline over critical PHP vulnerabilities
- Patchstack: the October PHP vulnerability timeline
- Google Threat Intelligence Group: vulnerability discovery and exploitation trends in the AI era
- Qualys: nginx2root, five nginx flaws fixed on 18 November
- WordPress: version 7.1.5
- Patchstack: the PHP November 2026 security release
This article was written on 21 November 2026. The details of the November releases, including whether any of the flaws are being attacked, may have changed since.