codebind
All articles
AI just broke PHP. Is your website next?

AI just broke PHP. Is your website next?

On October 21, 2026, the PHP project shipped an emergency security release. It fixed two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619, that let an attacker run code on a server without logging in. No password, no stolen account, just a crafted web request.

PHP is not a niche technology. It powers WordPress, Drupal, Joomla, Magento, most shared hosting and countless custom sites. Wiz, one of the security firms behind the discovery, estimates that roughly 70% of the web runs on it.

Found by AI, after hiding for more than ten years

The flaws had been sitting in the PHP engine for over a decade. Every PHP version going back to 5.4 is affected by at least one of them.

What changed is AI. Researchers at Calif and Wiz, working with frontier AI models through OpenAI's Patch the Planet program, found and weaponized them in a matter of weeks. In Wiz's own words, frontier models made it possible to "develop and adapt working exploits across multiple applications in hours".

Wiz then built a single exploit script and showed it could take over fresh installs of WordPress, Drupal and Joomla with nothing but default settings. Even a simple "Hello World" page on an affected PHP version could be vulnerable, because the bug is in PHP itself, not in the website code.

The same research showed attackers could also read server memory: passwords, session tokens, API keys and certificates belonging to other visitors.

Governments pulled the plug

When details leaked a day before the official fix, agencies around the world reacted fast. The UK's National Cyber Security Centre, the US NSA, CERT-EU, Japan and Australia all gave the same advice: patch immediately, or take the site offline until you can.

Many did exactly that. According to the BBC:

  • Finland temporarily shut down the government's public web services.
  • The Netherlands' cyber security agency took its own website offline, and the site of the Dutch parliament's lower house became inaccessible.
  • The Wikimedia Foundation took several systems down as a precaution, leaving parts of Wikipedia unreachable.

Cloudflare reported seeing early attacks within hours of the disclosure.

The real problem: old PHP never gets fixed

Patches exist for PHP 8.2, 8.3, 8.4 and 8.5. But PHP 8.1 and everything older will never receive a fix. Those versions are end of life, and the only way out is to migrate.

That is the uncomfortable truth for a huge number of business websites:

  • Built years ago by an agency that no longer exists
  • Running on a shared host that nobody logs into
  • Using an old plugin or theme that only works on an old PHP version

Updating PHP on these sites often breaks them. So they stay on the vulnerable version, and with AI tools now able to find and exploit legacy code at this speed, they are sitting targets.

What you should do now

  1. Check your PHP version. Your host's control panel usually shows it. Anything below 8.2.35 is exposed.
  2. Update or isolate. If you are on a supported branch, update today. If not, consider taking the site offline until it is migrated, as the security agencies recommend.
  3. Assume you may already be compromised if your site was exposed. Rotate passwords and API keys and check for unknown admin accounts.
  4. Plan the move off legacy code. A patch fixes this bug. It does not fix a codebase that nobody can safely update.

How codebind can help

We migrate legacy PHP and WordPress sites to a modern, fast and secure Node.js stack with a small attack surface and dependencies that are kept up to date. Your content and SEO move with you.

Use Refactor Website on our homepage, enter your current URL, and we will send you a quote.


Sources: The PHP Foundation, Wiz Research, OpenAI, BBC News.