The digital landscape is currently navigating a period of significant instability as system administrators and web developers scramble to address a pair of catastrophic vulnerabilities in PHP. These flaws, which allow attackers to seize full control over affected servers, have triggered a global race to patch systems. With nearly 70 percent of all websites reliant on PHP—the foundational programming language for giants like WordPress, Drupal, Magento, and Joomla—the scale of the threat is immense. Experts are warning that the bugs are already being actively exploited in the wild, leaving countless websites at risk of defacement, data theft, and total system compromise.
The vulnerabilities, tracked as CVE-2026-109618 and CVE-2026-109619, are classified as critical. Because they reside within the core of the PHP language itself, their impact is not limited to a single application or plugin; rather, they compromise the underlying infrastructure of the internet. Following the public disclosure of these flaws, an emergency security update was released to address the issues. However, the sheer ubiquity of PHP means that the patching process will be complex, time-consuming, and potentially fraught with further instability as administrators rush to deploy fixes.
A New Class of Exploitation
The discovery of these vulnerabilities marks a turning point in cybersecurity, largely due to the role of artificial intelligence in the research process. According to a detailed analysis by security firm Wiz—one of the organizations involved in the discovery—the underlying flaws had technically existed for decades. However, they remained dormant because the chain of events required to successfully exploit them was exceptionally complex, sitting at the very edge of what human researchers could practically achieve.
Wiz researchers noted that frontier AI models significantly lowered the barrier to entry, effectively transforming a long-standing, theoretical architectural flaw into a weaponized exploit. This evolution suggests that the window of time between the discovery of a vulnerability and the development of a functional, mass-scale exploit is shrinking rapidly. The team at Wiz has described these findings as ranking among the most severe in software history, emphasizing that the "PHP2Shell" style of attack—which allows for the installation of web-based backdoors—is likely to be the primary method used by threat actors to maintain persistence on infected systems.
Widespread Impact and Early Signs of Chaos
The fallout from these vulnerabilities was almost immediate. Reports from Reuters and other outlets confirmed that several government websites across Europe and beyond were forced offline shortly after the vulnerabilities were disclosed, likely as a precautionary measure to prevent compromise. Security firm Cloudflare, which monitors a massive portion of global web traffic, reported detecting exploitation attempts in the early morning hours. By 3:02 am UTC, the company had implemented emergency web application firewall (WAF) rules designed to intercept and neutralize attack traffic specifically targeting these vulnerabilities.
The risks posed by these bugs are multifaceted. An attacker who successfully exploits these flaws can gain remote code execution capabilities, allowing them to run arbitrary commands on the server. This leads to several immediate threats: the total denial of service (DoS) of the targeted website, the exfiltration of sensitive databases and user information, and the installation of "web shells." These web shells act as a persistent remote control panel, granting attackers ongoing, unauthorized access to the server long after the initial exploit has occurred.
Measuring the Scope of the Threat
The sheer volume of potentially affected systems is staggering. Censys, a technology tracking firm, performed a scan of the internet landscape and identified approximately 2.58 million internet-facing hosts and 54.9 million individual web properties running on PHP. Because PHP is so deeply woven into the architecture of modern web publishing, it is not merely a matter of updating one central software package; rather, it requires a coordinated effort across hosting providers, cloud platforms, content delivery networks (CDNs), and individual site owners.
Industry experts are already drawing comparisons to the infamous Log4Shell vulnerability that paralyzed the internet in 2021. Much like the Log4j logging framework, PHP is a fundamental building block that is frequently overlooked by end-users, even though it serves as the backbone of their digital operations. "A vulnerability in core PHP reaches far beyond a single application," the Wiz researchers stated in their advisory. "PHP runs across clouds, hosting providers, content-delivery networks, and millions of independently managed servers. Reducing exposure before the technical details became public required coordinated work across that entire ecosystem."

OpenAI, which contributed to the research and outreach efforts regarding these vulnerabilities, echoed these concerns. Given the extreme severity of the flaws and the near-total reliance of the web on PHP, the organization has characterized this event as one of the most impactful security issues in recent memory.
The Path to Remediation
The PHP development team has moved quickly to provide fixes. The vulnerabilities are addressed in PHP versions 8.5.12, 8.4.27, 8.3.36, and 8.2.35. All web servers running any version of PHP 5.4 or later are considered affected, making this a massive-scale update requirement.
Organizations are urged to audit their environments immediately to determine their current PHP version and apply the necessary patches. The SANS Internet Storm Center is currently monitoring major software platforms and distribution channels to ensure that updated packages are being pushed out effectively. For instance, Ubuntu has already begun releasing updated PHP packages to its users, and other distributions are expected to follow suit.
However, security professionals warn that the patch is only the first step. Because these vulnerabilities can be used to install web-based backdoors, administrators must not only update their core software but also conduct thorough integrity checks of their file systems to ensure that no malicious web shells were introduced during the period between the vulnerability’s discovery and the deployment of the patch. If a server was compromised before the update was applied, simply installing the patch will not remove the attacker’s existing access.
Looking Ahead
As the situation unfolds, the tech community is analyzing the discovery process for lessons on how to better prepare for future threats. The collaborative effort between organizations like Wiz, OpenAI, and the PHP team to coordinate disclosure and measure the scope of the problem is being viewed as a model for future large-scale vulnerability management. Calif, another organization involved in the discovery, has even published a detailed, comic-book-style technical deep dive into the discovery timeline, aiming to make the complex mechanics of the vulnerability accessible to a broader audience of developers.
Despite these efforts, the reality remains that the internet will remain in a state of high alert for the foreseeable future. The combination of active, in-the-wild exploitation and the massive number of unpatched servers suggests that we are entering a period of significant digital volatility. Web administrators are advised to prioritize these updates above all other maintenance tasks. For those who cannot patch immediately, implementing robust WAF rules—as suggested by services like Cloudflare—may provide a temporary buffer against the most common automated attack vectors.
As of this afternoon, the situation continues to evolve. Security teams globally remain on high alert, and the focus has shifted from initial disclosure to a long, grinding process of remediation and forensic analysis. Organizations are encouraged to monitor their internal security logs for suspicious activity and to verify that all PHP-dependent applications are running the latest, patched versions of the language. In a digital environment where the underlying code is the foundation for almost every major online service, the security of PHP remains a critical, ongoing concern for the entire web ecosystem.

