PHP Security Exposes the Cost of Underfunded Maintenance and Outdated Servers

| 2 Min Read
PHP’s staffing crunch slowed a security fix, while years-old installations made patching far harder across the web.

PHP’s latest security incident points to two problems that compound each other: a small core team and a web full of installations too old to patch easily. The language runs about 71% of websites, yet the PHP Foundation reportedly has one full-time employee and 14 contractors who work mostly part time. That gap matters because software maintenance depends on more than writing a fix; it also requires reviewing reports, coordinating releases, and helping users understand what to change.

The incident also shows why a vulnerability’s technical scope and its practical reach can diverge. A patch may be straightforward for a current installation, while organizations running old versions face code changes, compatibility checks, and deployment work. The result is a security problem shaped by both the people maintaining PHP and the long tail of systems depending on it.

A small team, a delayed fix

Executive Director Elizabeth Barron told Reuters that she is the Foundation’s sole full-time staff member. The team maintains PHP’s core, including security fixes, and accepts outside contributions. That model resembles open-source projects such as Linux, but Linux has many more full-time contributors, including developers employed by companies that depend on it. The comparison points to a familiar tension: open-source software can support a vast commercial ecosystem while its day-to-day maintenance rests on a much smaller group.

PHP already had a stretched development team before AI tools helped drive a surge in vulnerability reports. More reports can improve the chances that flaws get noticed, but each credible issue still needs investigation, validation, and a coordinated response. Those steps compete for time with ordinary development and maintenance. When the people doing that work are few, even a well-understood problem can wait.

Barron said there was no reported exploitation of PHP2Shell before a security fix was released. Still, the underlying out-of-memory flaw had been identified in 2024, and work to resolve it “stalled and restarted repeatedly over months.” That history makes the delay more revealing than the release of the patch itself: identifying a vulnerability doesn’t guarantee that a project has enough uninterrupted capacity to finish the work.

The PHP Foundation described the delay as a “structural failure.” The scale of PHP deployments and their third-party extensions added to the work, while Chainguard accidentally disclosed details before the coordinated release embargo ended. Foundation funding helped multiple people work on the issue full time, including over weekends, as they coordinated with other parties. The episode shows how security response depends on a chain of tasks, from reproducing a flaw to preparing compatible fixes and communicating them before details spread.

That support matters, but the incident also raises a practical question for companies that rely on PHP: whether they’ll contribute more to maintaining the language their businesses run on. Open-source projects often receive broad use without receiving support in proportion to that use. This is more significant than it looks: a thin maintenance budget can become a bottleneck for every organization waiting on the same fix.

Old installations made the exposure worse

For servers running a current PHP 8 release, the fix was only a point update away. Yet some websites went offline for hours or days as operators weighed the risk of leaving systems exposed. That choice reflects the operational cost of updating production software: teams may need to check application behavior, test extensions, and plan a deployment that avoids disrupting users. A small update can still demand substantial preparation when the surrounding system is old or poorly documented.

The bigger obstacle was the age of the installations: a Flare.io analysis found that nearly 73% of PHP installations were on versions past end of life, where fixes are much harder to obtain. End of life changes the maintenance equation. Operators may be unable to apply current security updates through ordinary channels, and moving to a supported release can require changes across the application stack.

Many of those systems still ran PHP 7, whose support ended four years ago. The release first appeared in late 2015, giving operators years of notice before its retirement. About 7.7% of PHP sites were still using PHP 5, a branch introduced in 2005 and retired in 2018. Those figures describe accumulated maintenance decisions: the software may keep serving pages, but continued operation doesn’t mean it remains easy to secure.

Moving between major PHP versions can require changes to website code, but much of that work involves replacing old functions and libraries that had been marked for deprecation. Automated tools such as Rector have been available to help with upgrades, and many newer PHP features were designed to make error-prone code clearer. Tools can reduce repetitive work, but they can’t remove the need to test an application’s behavior or decide which upgrades the business can schedule.

Maintenance is the larger risk

The staffing shortage made it harder to resolve the core vulnerability quickly. But the scale of outdated deployments turned a patch into a much broader operational problem. A fix cannot protect systems that operators can’t readily upgrade or that no longer receive supported updates. The risk therefore sits at two levels: the project needs capacity to produce fixes, and organizations need a workable path to install them.

PHP’s incident shows how quickly those weaknesses can converge: a lean maintenance team faces more security reports, while years of deferred upgrades leave a large share of deployments exposed. And this is the part most people overlook: security work doesn’t end when maintainers publish a patch. Operators still have to find affected systems, assess compatibility, and complete the upgrade. If you’re working in this space, the practical lesson is to treat version support as an ongoing maintenance decision, not a one-time migration project.

What the incident means for PHP’s future

The episode puts pressure on both sides of the maintenance relationship. The Foundation’s limited staffing makes sustained outside support important, while the old installations show that users also need to budget time for upgrades before an emergency forces the issue. Neither problem has a quick technical fix. More people can help a project respond, but organizations still have to keep their own deployments within supported versions.

That said, the numbers here are underwhelming for an ecosystem with PHP’s reach: widespread dependence hasn’t translated into a similarly broad base of current installations or full-time maintenance capacity. The incident is a reminder that open-source software’s apparent availability can conceal concentrated labor and years of deferred upkeep. A patch closes a vulnerability in supported code. Keeping the wider web protected takes ongoing work.

Not a one-off cleanup.

Source: [email protected] (Bruno Ferreira) · www.tomshardware.com

Comments

Please sign in to comment.