Intelligence · State of PHP · 2026
PHP in Europe: The Invisible Patch
Who secures the European Web?
Following PHP2Shell, the hosting industry anticipated a measurable wave of site migrations to higher PHP versions. However, ShareShift data points at strong inertia of the web that far outweighs reactive security patching. In this article, we unpack the true state of PHP in Europe and the implications of invisible maintenance for hosting operators.
Target
Hosting product & commercial leaders
Publication date
November 2026
Author
Nadya Frost
Executive summary
The expectation that a critical flaw like PHP2Shell (fixed in late October 2026) would trigger a massive ecosystem upgrade is not supported by the data. When evaluating the European web across a four-week rolling scan window, the market share of unsupported PHP versions remained stubbornly high at approximately 40%. The vast majority of the European web sits exactly where it was deployed.
However, old versions no longer equal vulnerable sites, provided the host is silently backporting fixes. This means that any external count of old PHP overstates exposure wherever hosts backport, and understates it wherever they do not.
And most customers are completely unaware of this dynamic. A host providing invisible backports is delivering massive value that goes entirely unrecognized. Every hosting operator should be aware of the size of their PHP footprint, and - if sizeable - monetize this type of mandatory, invisible security effort.
The True Age of the European PHP Base
ShareShift scans European ccTLD domains on a rolling basis. By late October 2026, the snapshot of domains disclosing their PHP version reveals a top-heavy but deeply entrenched legacy tail.
Overall, roughly 40% of sites disclosing their PHP version run on a branch that the PHP project no longer actively supports. While modern branches (8.2 through 8.5) constitute the majority, the persistence of 7.x and 5.x branches remains a permanent fixture of the ecosystem.
Data table
| Name | Numeric Key |
|---|---|
| 8.5 | 8.4% |
| 8.2-8.4 | 51.1% |
| 8.0-8.1 | 11% |
| 7.x | 21.8% |
| 5.x | 7.7% |
- 8.58.4%
- 8.2-8.451.1%
- 8.0-8.111.0%
- 7.x21.8%
- 5.x7.7%
| PHP branch | Official status, Nov 2026 | Share of detected sites |
|---|---|---|
| 8.2 to 8.5 | Fixed upstream in 8.2.35, 8.3.36, 8.4.27 and 8.5.12 | 59.5% |
| of which 8.5 | Active support | 8.4% |
| 8.0 and 8.1 | End of life. Minimal source backports only | 11.0% |
| 7.x | End of life. Source backports for 7.4 only, none for 7.3 and older | 21.8% |
| 5.x | End of life. No fix from PHP | 7.7% |
Why is old PHP not the same as exposed PHP?
Because a version string describes the software someone installed, not the fixes someone applied to it.
The PHP project fixed PHP2Shell in 8.2.35 and higher; for 7.4, 8.0 and 8.1 it offers only minimal source backports, and for 7.3 and older nothing. Hosting stacks fill that gap. According to Topsitehosters' timeline of the industry response, cPanel's EasyApache 4 backported fixes for 7.4, 8.0 and 8.1, and CloudLinux shipped fixed alt-php builds from 5.2 to 8.5. Other hosts did the same for older branches.
So the same version string can mean three different things:
| Population | Same version string, different state | Who can tell |
|---|---|---|
| Patched upstream | Version changed to 8.2.35 or later | Anyone with a scanner |
| Patched by the host | Version string unchanged, build patched | Only the host |
| Unpatched | Version string unchanged, build vulnerable | Only the host |
What should an operator do with this?
For hosting operators, ShareShift has produced three ready playbooks for extracting incremental revenue from legacy tech stack maintenance. Each one has a clear Segment + Campaign + Business Case you can adapt to your needs.
Can you tell customers which of the three populations they are in?
If your PHP is backported, say so in plain language. It is a product feature that competitors can only guess at. Name it and charge a premium. See how in playbook 1: Hardened PHP.
Are you giving away the 'Invisible Patch' for free?
If 40% of the web refuses to upgrade, hosts are forced into perpetual maintenance. That backend effort needs to be packaged and monetized as a premium security tier. See playbook 2: The Security Bundle.
How does old PHP fit with Managed WP?
Updating PHP is only one step in keeping WP up to date; for holistic results, offer "maintain" and "manage" WordPress offerings. Your customers will appreciate the service. Calculate your upside in playbook 3.
Methodology
ShareShift scans European ccTLD domains (DNS, HTTP and TLS), and enriches this information with 100+ technology signals. For more information about our scanners, please visit the Methodology section. Public figures come from the sources cited inline.
Visibility limits
The unit is any site that discloses a PHP version. Sites that hide it (via expose_php = off or edge caching) may be better or worse maintained, and we cannot see which.
PHP version
PHP branch is read from server-disclosed version strings and grouped to major and minor branch. The snapshot data utilizes the scan period concluding October 28, 2026.
Appendix: Related Research