From our team

What Happened to PHP?

What Happened to PHP? Inside the Security Crisis That Shook the Internet

How two critical vulnerabilities exposed the risks of relying on one of the internet’s most widely used programming languages.

On 21 October 2026, PHP, one of the technologies that quietly powers a significant portion of the internet, became the focus of a major cybersecurity incident. Two critical security vulnerabilities triggered urgent warnings, disrupted government websites and forced organisations to take action to protect their systems.

The incident raised an important question: How could a programming language that has powered websites for decades become the source of such a serious security crisis? And what does this mean for the millions of websites and applications that depend on it?

The answer goes beyond a coding error. It involves software security, legacy infrastructure, limited development resources and the growing role of artificial intelligence in discovering vulnerabilities.

First, What Is PHP?

PHP, originally known as Personal Home Page Tools and now commonly associated with PHP: Hypertext Preprocessor, is an open-source programming language designed primarily for server-side web development.

Whenever someone logs into a website, submits a form, checks an online account or purchases a product, PHP may be working behind the scenes to process the request and communicate with a database.

It powers WordPress, which underpins a substantial share of websites worldwide, alongside many online shops, content management systems, business applications and government portals.

PHP became popular because it is accessible, relatively inexpensive to deploy and supported by a large developer community. Its widespread adoption, however, also means that a serious vulnerability can have consequences far beyond a single organisation.

What Actually Happened?

On 21 October 2026, reports emerged of two critical vulnerabilities affecting PHP. Both were assigned severity ratings of 9.2 out of 10, reflecting the potential seriousness of the flaws.

According to reporting by Reuters, the vulnerabilities could allow unauthenticated attackers to execute commands remotely on affected servers. Depending on the system and its configuration, successful exploitation could lead to data theft, website defacement or a complete compromise of a server.

The discovery prompted urgent security warnings and disrupted services as organisations assessed their exposure and worked to secure affected systems. Some government websites in Europe experienced outages while protective measures were implemented.

The response demonstrated an uncomfortable reality: when a widely deployed technology has a critical vulnerability, taking a website offline temporarily may be safer than leaving it exposed to attackers.

Sources: Reuters, 21 October 2026; Associated Press, 22 October 2026.

The Most Concerning Part: The Vulnerabilities Were Not New

One of the most troubling aspects of the incident was the reported age of the underlying flaws.

Security researchers indicated that the vulnerabilities had existed for years, with reports suggesting they dated back to at least 2024. Yet identifying a potential weakness and proving that it can be exploited reliably are two different challenges.

A vulnerability can remain undiscovered, misunderstood or insufficiently prioritised for a long time. During that period, the affected software may be deployed across thousands or even millions of systems.

The incident raised questions about how such weaknesses remained unresolved and whether the processes used to review, maintain and secure widely deployed software are adequately resourced.

It also highlighted an important distinction: a vulnerability existing in the code does not automatically mean every PHP website is vulnerable. Exposure depends on the affected component, the installed PHP version, configuration and whether the relevant fixes have been applied.

How Artificial Intelligence Changed the Investigation

Artificial intelligence played a significant role in identifying and investigating the vulnerabilities.

According to reports, researchers used AI-assisted techniques to uncover weaknesses and help validate potential exploits. OpenAI worked with a coalition of researchers and security organisations, while cybersecurity company Wiz independently identified another vulnerability.

This illustrates both the promise and the danger of AI in cybersecurity.

For defenders, AI can help researchers analyse large amounts of code, identify suspicious patterns and investigate weaknesses that might otherwise remain hidden. For attackers, similar capabilities can potentially accelerate the discovery of exploitable systems.

AI does not eliminate the need for human expertise. Researchers must still determine whether a suspected flaw is real, establish its impact, develop reliable fixes and ensure that those fixes do not introduce additional problems.

The PHP incident offers a glimpse of a future in which vulnerabilities that survived years of conventional review may be discovered much faster through AI-assisted security research.

Was PHP the Problem, or Was It the Way the Ecosystem Was Maintained?

It would be misleading to conclude that PHP is inherently unsafe simply because serious vulnerabilities were discovered in it.

Every major programming language and software platform can contain security defects. The more important questions are how quickly vulnerabilities are identified, how effectively fixes are developed and distributed, and how consistently organisations install those fixes.

However, this incident also exposed concerns about the resources available to maintain PHP itself.

In an October 2026 report, Reuters described the PHP Foundation as severely underfunded relative to the importance of the language it supports. The foundation's executive director reported that the organisation had just one full-time employee, supported by mostly part-time contractors.

The foundation depends on sponsorships, donations and grants to support development and security work. Meanwhile, PHP remains a foundational technology for a substantial portion of the internet.

This creates a difficult imbalance: the economic value supported by a technology can be enormous, while the resources dedicated to maintaining its underlying open-source code remain comparatively limited.

The lesson extends beyond PHP. Many businesses depend on open-source projects that are maintained by small teams and volunteers, often without a level of funding proportionate to their importance.

What Does This Mean for WordPress and Other PHP Applications?

The incident is particularly relevant to WordPress users, web hosting providers, software developers and organisations running custom PHP applications.

A website can be well designed, use strong passwords and have reliable backups, yet remain exposed if its underlying runtime contains an unpatched vulnerability.

Organisations should therefore treat the incident as a software supply-chain security issue, rather than assuming that updating their website's content management system alone will resolve it.

Automatic WordPress updates, for example, do not necessarily update the PHP runtime installed on the server. The server administrator or hosting provider must ensure that the affected PHP components are patched.

Organisations should:

  • Identify affected systems: Inventory PHP versions, applications, frameworks and hosting environments.
  • Apply official security updates: Follow the PHP team's advisories and vendor guidance for the affected versions.
  • Review exposure: Prioritise internet-facing systems and investigate suspicious activity where appropriate.
  • Use temporary mitigations: If a system cannot be patched safely and remains vulnerable, restrict access or take it offline when necessary.
  • Test before restoring service: Confirm that fixes work correctly and that business-critical applications remain functional.
  • Improve long-term maintenance: Establish clear ownership for runtime updates, vulnerability monitoring, backups and incident response.

Organisations should also check whether any compromised systems require investigation and recovery, rather than assuming that installing a patch automatically reverses any damage that may already have occurred.

Is This the End of PHP?

No. The incident does not mean PHP is disappearing or that every PHP-powered website is compromised.

PHP continues to be actively developed, and modern releases have introduced significant improvements in performance, language features and maintainability. Its extensive ecosystem means that replacing it everywhere would be expensive and, in many cases, unnecessary.

The immediate priority is to identify affected systems, apply the appropriate fixes and investigate possible compromises. The longer-term priority is to strengthen the processes and resources that keep the language secure.

Nevertheless, the incident may encourage some organisations to reconsider how they manage legacy applications, choose software versions and allocate budgets for security maintenance.

For businesses operating critical systems, the question should not simply be whether PHP remains a viable technology. It should be whether the organisation has the resources, technical discipline and upgrade strategy needed to operate it securely.

The Bigger Lesson: The Internet Is Only as Strong as Its Maintenance

The PHP security crisis is a reminder that digital infrastructure rarely fails because of a single factor.

A vulnerability may originate in a line of code, but the consequences depend on how widely that code is deployed, how long the weakness remains undiscovered, how quickly a fix becomes available and how effectively organisations respond.

The incident also demonstrates that open-source software is not automatically secure simply because its code is publicly available. Transparency creates opportunities for scrutiny, but effective security still requires skilled contributors, sustained funding, responsible disclosure and timely updates.

Artificial intelligence may help uncover weaknesses more quickly than before. That makes the ability to respond quickly even more important.

The real lesson is not that PHP has failed. It is that the systems supporting our digital world require continuous investment, maintenance and accountability. A programming language can be reliable for decades and still face serious vulnerabilities. What matters is whether its community and the organisations that depend on it can identify, fix and manage those risks before they become widespread incidents.

PHP has helped build the modern web. Its latest security crisis is a warning that maintaining that achievement requires more than writing good code: it requires treating software security as an ongoing responsibility.

Sources for Further Reading


Editorial note: This article focuses on the October 2026 security incident, rather than the broader history of PHP.

Build with us

Have a project in mind?

We design, build and integrate APIs, web and mobile apps for businesses of all sizes.

Start a project