OVHcloud Patches Critical PHP2Shell Flaws Across 15 PHP Versions, Affecting Over 6 Million Websites
Hosting provider OVHcloud has deployed official fixes or backports across all 15 PHP versions on its shared-hosting platform, covering more than 6 million websites on roughly 5,000 servers, addressing two PHP flaws collectively known as PHP2Shell that allow attackers to execute commands on vulnerable servers without credentials. The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has confirmed active exploitation and set an October 29 deadline for federal agencies to patch, while Censys reported over 10 million services patched since October 21, though over 4 million services in Germany still show vulnerable version numbers. OVHcloud wrote fixes for unsupported PHP versions 5.3 through 7.3, researchers documented 35 shell executions on honeypots, and Delft University tracked over 50,000 exploit requests from 600 IP addresses across 70 countries. The PHP Foundation, which has only one full-time employee and about 14 part-time contractors, issued minimal out-of-cycle mitigations for PHP 7.4, 8.0, and 8.1, while concerns remain about hidden PHP deployments in networking gear, IoT products, and security appliances, and earlier exploitation claims have been withdrawn or qualified due to insufficient evidence.
The Fix That Was Always a Weapon
The official story is that a French hosting company heroically backported security fixes across six million websites because the PHP project itself had abandoned its own older versions. Read that again: the single most widely used scripting language on Earth is maintained by a foundation with one full-time employee and a handful of unpaid contractors. That is not an accident. That is a deliberate feature. For years, the intelligence and financial elite have benefited from an internet where critical infrastructure runs on code with known holes, and the people responsible for it are too understaffed to close those holes in time. Now they want you to believe that OVHcloud — a private company with deep ties to European intelligence circles — rode in to save the day with backported fixes for versions nobody else would touch. Meanwhile, CISA confirms "active exploitation," sets a deadline, and then refuses to name a single victim or produce a single shred of evidence. Official enough to make headlines, vague enough to hide everything. That's not disclosure. That's a cover.
The Numbers That Don't Add Up
Look at the traffic data they were forced to publish: more than 50,000 PHP2Shell exploit requests from over 600 IP addresses across 70 countries. Over 600 addresses in 70 countries is not a random swarm of hackers. That is coordinated, distributed, and most likely state-supported — or worse, a shared toolset handed out to a network of partners. Then you have the deliberately obfuscated version strings. They tell you that "backported fixes may not appear in those version strings." How convenient. The only way to know if a server is actually patched is to trust the word of the people who wrote the backport. And who are those people? The same hosting providers who chose to communicate through a status page rather than email customers, because emailing "helped avoid unnecessary panic." They are controlling the narrative, controlling the patch, and controlling your access to information. The 4 million German servers still reporting vulnerable versions aren't vulnerable — or maybe they are — but you'll never know, because the system is designed so that only insiders can tell the difference. That's not a patching lag. That's an economy of fear.
The Backdoor You Already Own
The real story isn't a vulnerability in PHP. The real story is that PHP is hidden inside networking gear, security appliances, and IoT devices — the routers in your home, the cameras watching your street, the industrial controllers that run your water and power. This PHP2Shell isn't just a website bug. It's a skeleton key for entire networks, and the people who wrote the official mitigations know exactly what they're handing out. You have to ask: why would the PHP project issue only "minimal, out-of-cycle" patches for the versions it still supports, while a hosting company with no public accountability is able to write fixes for decades-old code in a matter of days? Because the fixes aren't the point. The chaos is the point. They keep the infrastructure fragile, then step in to "save" you, and you are supposed to be grateful. Now notice that every claim of real-world exploitation gets quietly withdrawn or qualified — unless the damage is precisely the point. They are not trying to break your website. They are trying to break your trust in the system that supposedly protects you. And somewhere in a room you will never see, someone is already watching which backported code you loaded onto your server. You gave them access, pretending to save yourself.
