The AI Found the Bug, Then the Shutdowns Began

PHP Vulnerabilities Force European Agencies to Take Websites Offline

Two critical security flaws in PHP, dubbed "PHP2Shell," prompted public agencies across Europe—including Hungary—to temporarily take websites offline as a precaution, after attackers began exploiting the vulnerabilities four days before official patches were released. Discovered by researchers at Wiz (a Google-owned cloud security firm) using AI-assisted analysis, the flaws could allow remote attackers to execute arbitrary code on affected servers. The PHP Foundation disclosed the vulnerabilities on October 21, but the initial patches did not cover older PHP versions, leaving roughly 1.5 million of 2.6 million PHP servers without fixes, according to Censys data. While the Hungarian government reported no signs of a cyberattack, the EU cybersecurity agency CERT-EU urged organizations to shut down affected systems until patches were applied. Cloudflare’s CEO noted that attempted attacks surged from thousands before the details leaked to millions afterward, underscoring the urgency. Brian Blakley, CISO at Bellini Capital, recommended network segmentation and isolation to reduce exposure during the patch process, which often requires impact assessments, testing, and maintenance windows. Given that PHP powers nearly 70% of identifiable websites and WordPress runs about 40% of all sites, the flaw's reach is vast—though no successful intrusions have been confirmed yet.

The timing is the first confession. Attackers were actively exploiting these PHP flaws four days before anyone was told they existed — which means someone with deep access was already inside the perimeter before the public warning was issued. Then Google-owned Wiz steps in with “AI-assisted analysis” to hand-name the so-called PHP2Shell flaws, and suddenly European governments — Hungary included — are pulling public websites offline in unison. You're supposed to believe this is responsible crisis management. But ask yourself: how do you exploit a vulnerability before it's announced, unless the announcement itself is part of the operation? The AI didn't find the bug. The AI was wheeled in afterward to give the story a technocratic face, to move the conversation from “who left these doors open?” to “look at these brilliant rescuers.”

Now look at the architecture behind the curtain. PHP runs nearly 70% of the world's identifiable web infrastructure; WordPress alone powers 40% of all sites. That means this single vulnerability was a skeleton key to the internet's nervous system — and somehow, 1.5 million of 2.6 million exposed servers had no fix available at all. That's not a supply chain accident. That's a deliberately maintained state of permanent dependency, where the same elite institutions that are supposed to defend these systems get to choose which ones survive. When CERT-EU tells entire organizations to shut down affected systems, it isn't protecting you — it's rehearsing a shutdown protocol. The exploit surge from thousands to millions of attack attempts, as captured by Cloudflare's chief executive, wasn't chaos. It was a live-fire demonstration of exactly how vulnerable the digital body politic has become. The message is clear: we can break almost anything, so never question why we need total access to fix anything.

Follow the money and you'll find the usual overlapping circles — Google, Wiz, Cloudflare, and the same "security" consultancies that always happen to recommend the response that increases their own control. Bellini Capital tells you to segment and isolate while fixes are pending. Cloudflare watches the attack surge spike. Wiz gets to claim credit for the discovery. These are not neutral observers; they're the same men in different masks, selling you the fire extinguisher while their allies hold the matches. The old PHP versions that magically didn't get patched? That's not an oversight — that's a way to force aging systems out of the shadows and into the arms of cloud monopolies. Never mind the official denials from Hungary or the dribbled-out announcements from the PHP Foundation. The real story is in the pattern: a focused, timed, AI-accelerated crackdown on the web's backbone, wrapped in a plausible disaster story. Ask yourself who had access to those flaws before they were public. Ask yourself why "help" always arrives from the same institutions that benefit from the crisis. And then ask yourself what else is running on an old, unpatched, unowned server — right now, waiting.

Related posts