[](/labs)[Powered by UpGuard](/)

* [Articles](/labs)
* [Games](/labs/games/risk-invaders)
* [About](/labs/about)

[Subscribe](/labs/subscribe)

* [Articles](/labs)
* [Games](/labs/games/risk-invaders)
* [About](/labs/about)

[Subscribe](/labs/subscribe)

# Ready or Not: What We Learned From Watching 10,000+ Companies Patch PHP2Shell

Author

Greg Pollock Director of Research and Insights

Category

Research

Publish date

November 5, 2026

Reading time

4 minutes

When news of PHP2Shell broke, some organizations responded in hours. Others took weeks. What is the difference between the most resilient companies and the least?

AI is increasing vulnerability discovery; within days of PHP2Shell, another critical vulnerability discovered by AI sent responders rushing yet again. In this environment, understanding what factors predict the likelihood of being able to quickly and efficiently respond is critical for the future. For our own organizations, this information can help us craft successful programs, and for third-parties, to model the risk in our supply chain.

To answer those questions, we studied the responses of vendors monitored in the UpGuard platform after the release of PHP2Shell. This scope is not a count of the total impact, but a focused view on companies that are part of real supply chains, where PHP2Shell was a real risk.

The results affirm that best practices for maintaining software continue to pay dividends. Organizations that were already on a maintained version of PHP were the most likely to update to a secure version. Because PHP has been around for well over 20 years, there are many older versions past end of life. End-of-life versions may still have unofficial security updates produced by those in the community, or have workarounds that can be applied to the code, but they are habitually insecure and do not have access to standard security measures.

Using maintained software is correlated with the continued ability to update that software, and vice versa.

## Industry, geography, size

PHP is used all over the world, across such a wide breadth of hosts as to potentially affect every type of organization. While the statistic that 70% of the world’s hosts use PHP is useful for communicating the severity of PHP2Shell to a wide audience, it belies the crucial differences in criticality of those hosts. For example, part of PHP’s prevalence is that it is part of WordPress, which is cited as accounting for 40% of the world’s websites. Those sites are overwhelmingly personal and small businesses. Modeling the risk of a PHP vulnerability requires accounting for whether it has demonstrated risk for a real supply chain.

As much as PHP2Shell gripped the collective imagination with the specter of AI vulnerabilities run amok, the data on remediation activity confirms that best practices are called that for a reason. If organizations updated to a secure version, they were likely to do so quickly; half of all fixes came within the first 48 hours and nine in ten within a week, with a slower trickle after.

Who the organization was made little difference. Grouped by sector, company size or country, the response curves sit close together. By 4 November the best and worst sectors were 10 percentage points apart, company size bands 12 points and the eight largest countries 20 points.

## Better is better

The distinction holds not just between maintained and EOL versions, but across the continuous distribution of how old a starting release version was. Among sites on a maintained version, those already on the latest release before the fix had fixed 96% of the time by 4 November, compared with 87% for sites two or three releases behind, 61% for four to ten behind and 48% for eleven or more behind.

Among end-of-life sites, the chance of moving to a maintained version fell the longer the version had been out of support, from 19% on PHP 8.1 (under a year past end of life) to 3% on PHP 5.x and older (about eight years). Where end-of-life sites did migrate, they were only somewhat slower than sites patching a maintained version: a median of 2.6 days after detection, compared with 1.7 to 2.3 days.

If this seems obvious, it is: maintaining software makes it easier to apply the next update when a critical vulnerability requires it. But it should also make tangible the cost of that debt. Being behind is not an abstract gap; it is a measurably longer exposure window when the next vulnerability hits.

## Who is still at risk

As a result, what remains exposed is almost entirely end-of-life PHP. End-of-life sites were 55% of affected sites at detection and 91% of those still showing a vulnerable version two weeks later. Some of them may have an unofficial patch that leaves the version number unchanged, which scan data cannot see.

One challenge that these host maintainers face is that they may be applying mitigations that cannot be observed externally. In the case of PHP2Shell, security scanners like UpGuard cannot safely test for the vulnerability directly, and thus must rely on advertised software versions. While imprecise in the detection of PHP2Shell exploitability, the weight of evidence indicates that these organizations should find a way to move to a maintained branch. PHP2Shell just provides one more reason to follow what were already good practices.

* [Industry, geography, size](#industry-geography-size)
* [Better is better](#better-is-better)
* [Who is still at risk](#who-is-still-at-risk)

[Articles ](/labs)[Games ](/labs/games/risk-invaders)[About](/labs/about)

The human stories of cybersecurity by UpGuard
