PHP: The three little letters wreaking havoc across the web

Two vulnerabilities in PHP, the scripting language used by a large share of the web, have prompted warnings from security researchers after sites including DeviantArt and 4Chan were temporarily taken offline following disclosure. By some counts, up to 70 percent of websites rely on PHP in some form. The affected software includes Wikipedia, WordPress and Drupal, and the reach extended to government systems as well.
The central problem is age and coverage. The flaw is present in every version of PHP dating back roughly 20 years, and many of those releases are no longer supported. That means patching is not a straightforward matter of updating a handful of servers. Older sites and services without active maintainers may have no practical remedy beyond shutting down for good.
Security firm Wiz described the issue as among the most severe vulnerabilities discovered in software history. A related exploit, referred to as PHP2Shell, reportedly hit Cloudflare hard, and the vulnerabilities were exploited in the days before a patch was available. The Internet Archive was briefly forced offline because of PHP, and two older Japanese mobile games are being shut down over the exploit. GPT-5.6 Sol was used to identify the critical flaw, according to the reporting.
This is a supply-chain problem in the plainest sense. PHP runs as an interpreter behind a web server, so a flaw in the language runtime sits underneath every application built on it, not inside any single app. Upgrading a CMS like WordPress or Drupal does not address the language layer itself; the runtime has to be replaced on the host. In practice that means inventories of which PHP versions run where, and how many of them are end-of-life, become the decisive operational question for teams responsible for legacy estates.
A likely trade-off is that unsupported codebases will increasingly be retired rather than patched, since the effort of moving an abandoned application onto a modern PHP release can exceed the value of keeping it online.
Why it matters: Teams running PHP applications, and especially those maintaining end-of-life versions, need to establish exactly where vulnerable runtimes sit in their infrastructure and weigh upgrades against retirement. The disruption to high-traffic sites and to long-running services suggests that old, unmaintained deployments are the hardest cases, and for product owners those may be the ones requiring a decision rather than a patch.
Based on reporting from the original publisher. Visit the source for full context and later updates.
Publisher excerpt
Two vulnerabilities found in the programming language PHP put enormous swaths of the internet in danger. By some accounts, up to 70 percent of websites use PHP in some capacity. It powers Wikipedia, WordPress, Drupal, and a host of other popular sites and platforms, including DeviantArt and 4Chan, which were temporarily shut down after the […]