Best Miami News connects businesses and publishers

collapse
Home / Daily News Analysis / PHP: The three letters that shut down sites all over the internet today

PHP: The three letters that shut down sites all over the internet today

Oct 23, 2026  Twila Rosenbaum 44 views
PHP: The three letters that shut down sites all over the internet today

The internet woke up to a severe security emergency this week as two critical vulnerabilities in PHP, the scripting language that powers a huge share of the web, forced major sites and services offline. The flaws, which can allow unauthenticated remote code execution, affected everything from community platforms and image-sharing sites to reference works, government agencies, and even online game services. The most alarming part is not simply that the bugs existed, but that they had reportedly sat unnoticed in PHP for roughly two decades before advanced artificial intelligence tools helped researchers turn a theoretical weakness into a practical attack chain.

The PHP Group warned that essentially any site running PHP could be at risk. Security researchers and cloud providers described the situation as one of the most serious software vulnerabilities in recent memory, and the warnings came with unusual urgency. Government cybersecurity agencies advised organizations to take systems offline if they could not patch immediately. Major hosting companies told customers to assume their PHP sites were affected and to update to fixed releases as soon as possible. For website owners, the message was blunt: check your PHP version, apply the patch, and if you handle sensitive data or sell products, consider taking the site down until your host has deployed a fix.

Key facts at a glance

  • Two critical PHP vulnerabilities were disclosed, both capable of unauthenticated remote code execution.
  • The flaws are tracked as CVE-2026-109618 and CVE-2026-109619, with associated advisory identifiers GHSA-w8hw-w9fx-j79w and GHSA-6wmf-4rv5-p3rp.
  • The vulnerabilities had existed in PHP for roughly 20 years, but exploitation previously required an exceptionally complex chain of steps.
  • AI security research played a central role: one group identified a critical PHP flaw using an advanced model, while another major security firm independently discovered and reported the vulnerabilities using AI.
  • PHP is used by about 69.3 percent of websites whose server-side programming language is known, according to W3Techs, and VirusTotal reportedly registers about 3.8 million sites running PHP with at least one port open.
  • Affected or precautionary outages included 4chan, DeviantArt, Wikipedia, Dutch and Finnish government agency sites, Pokémon Home, and Pokémon Champions.
  • The NSA Cybersecurity account on X and the UK National Cyber Security Centre recommended that organizations take systems offline if an immediate update was not feasible.
  • Cloudflare's chief technology officer said early attacks were already emerging.

What is PHP and why does it matter?

PHP is a widely used server-side programming language. It runs on web servers and generates the pages that visitors see, handles form submissions, manages sessions, connects to databases, and supports content management systems. Its reach is enormous because it underpins many popular platforms, including WordPress, which alone powers a large fraction of the web. W3Techs estimates that PHP is used by 69.3 percent of all websites whose server-side programming language is known. That includes major reference sites such as Wikipedia, community forums, publishing tools, and countless small blogs and business sites that may not have dedicated security teams.

VirusTotal data cited in coverage of the incident suggested that about 3.8 million sites were running PHP with at least one port open, offering a rough measure of the exposed surface. Not every one of those sites is vulnerable in the same way, and not every configuration will be exploitable. But the scale helps explain why a flaw in PHP can quickly become an internet-wide event. A vulnerability in a single application affects that application. A vulnerability in a language runtime or core library can affect millions of independent deployments at once, including sites that have no direct relationship with one another.

What happened?

The flaws were discovered through a combination of human security research and AI-assisted analysis. OpenAI said that an AI security group called Calif identified a critical PHP flaw using GPT-5.6 Sol. Google-owned Wiz independently discovered and reported the vulnerabilities using AI. The PHP Foundation acknowledged that an exploit for one of the vulnerabilities had been theorized in 2024, but said no concrete vectors were found at the time and that other issues with clearer impact overshadowed those concerns. That changed when more powerful AI models made it easier to turn an obscure bug into a dangerous vulnerability.

The PHP Group said attackers could use the two vulnerabilities for unauthenticated remote code execution. In practical terms, that means an attacker could run their own code on a vulnerable server without needing an administrator login or password. They could change content, access stored data, and potentially move deeper into the environment. The two flaws were described as RCE via OOM corruption and RCE via stale global state. The first involves out-of-memory handling that can interrupt PHP while internal request data is only partially initialized, after which request cleanup may treat invalid data as valid. The second involves request-owned internal state that can survive after its backing memory has been freed, allowing a later request handled by the same worker to use stale state before normal initialization resets it.

Why AI changed the risk

The vulnerability is not exactly new. It had been present in PHP for roughly 20 years. According to security firm Wiz, exploiting it required an exceptionally complex chain of steps, at the edge of what human researchers could practically achieve. That complexity helped keep the flaw obscure. It was not a simple missing password check or an obvious input validation error that automated scanners would catch immediately. Instead, it involved subtle interactions in memory handling and request lifecycle behavior, the kind of bug that can remain hidden for years because it is difficult to reason about and even harder to exploit reliably.

Powerful AI models have changed that calculus. They can help researchers analyze large codebases, identify unusual state transitions, and assemble exploit chains that would have taken enormous human effort to construct. The same capabilities that make AI useful for defensive research can also make obscure bugs more dangerous once they are revealed. In this case, the discovery itself was AI-assisted, and the public disclosure created a race between attackers and defenders. Once details are available, determined hackers can use AI tools to adapt the exploit, test variations, and target unpatched systems. That is why the warnings escalated so quickly from a technical advisory to operational advice about taking sites offline.

How serious is it?

The PHP Group said basically any site running PHP is at risk. OpenAI, which was involved in the vulnerability research, called it one of the most impactful security issues in recent memory. Wiz described it as among the most severe vulnerabilities discovered in software history. Those statements are extraordinary, but they reflect the combination of widespread exposure, unauthenticated remote code execution, and the relative ease with which attackers may now exploit the flaws.

The potential consequences go far beyond a defaced homepage. An attacker who gains remote code execution on a server could take full control of that server. That includes access to passwords, API keys, cryptographic certificates, and databases of sensitive information. With those credentials, an attacker could impersonate services, steal user data, or move laterally to other systems. The compromised server could also be turned into a vector for attacking other vulnerable servers, creating the conditions for a broader wave of intrusions. For organizations that run customer data, payment systems, or internal tools on PHP, the exposure is difficult to overstate.

The incident also demonstrated how quickly the effects can become visible. Sites and services took defensive action even when they were not confirmed to be compromised. Some Dutch and Finnish government agencies took their sites down as a precaution. The NSA Cybersecurity account on X recommended that organizations take their systems offline if an immediate update was not feasible, and the UK National Cyber Security Centre issued similar guidance. Pokémon Home and Pokémon Champions were taken offline. Coverage also noted that 4chan, DeviantArt, Wikipedia, and even a small neighborhood blog that posts pictures of dogs were caught up in the disruption. The range of affected sites, from global platforms to tiny personal projects, illustrates how deeply PHP is embedded in the web.

What site owners and users should do

For casual internet users, there is not much direct action to take. The vulnerability affects servers running PHP and does not necessarily target visitors directly. However, compromised sites could be used to spread malware or steal valuable data. Users who want to be extra cautious can check the social accounts of sites and services they frequently use to see whether those services have posted updates before visiting. That is especially relevant for sites that handle logins, payments, or personal information.

For website owners, the response is more urgent. Anyone running a website, even a simple blog, should check what version of PHP the site uses. Sites hosted on services such as Squarespace or Wix are in the clear because those platforms do not support PHP. Customers of hosting providers such as Hostinger, GoDaddy, Bluehost, or other web hosting services should be more cautious. GoDaddy said that any site using PHP should assume it is affected and update to the fixed release as soon as possible. It also said that sites running PHP 8.1 or older should upgrade to a newer version, because those versions are no longer supported and no official fix will be coming.

Those on managed hosting should check with their provider to find out when the fix will be deployed. If a site sells products or services, or if it stores any sensitive data at all, disabling the site until the host patches its version of PHP may be the safest immediate option. The disclosure also revealed that the vulnerabilities were exploited days before the patch, and the Internet Archive was briefly forced offline because of PHP. Two old-school Japanese mobile games were also shutting down over the exploit. Those developments show that the window between disclosure and exploitation can be extremely short, and that patching is not merely a best practice but an emergency measure. For organizations still running unsupported PHP versions, the absence of an official fix makes migration to a supported release even more critical.


Source:The Verge News


Share:

Your experience on this site will be improved by allowing cookies Cookie Policy