Blog · 18 November 2026 · 7 min read · for developers
Half the shops that advertise their PHP version run one that is past end of life
Every PHP branch gets security fixes for four years and then stops. In our November scans of small Polish online shops, 51 servers announce their exact PHP version to anyone who asks. 26 of them are on a branch that is already closed. If you build or maintain sites for clients, some of those are probably yours – here are the numbers, a script that checks a whole client list in a minute, and the upgrade order that keeps the shop selling.
What the scans showed
In November 2026 we scanned the home pages of 547 small Polish online shops (WooCommerce, PrestaShop and custom builds; no large chains). A server may add an X-Powered-By header with the PHP version – it does not have to, and most do not. On 17 November we re-requested every shop that did: 51 still send a version.
| PHP branch | Shops | Security fixes |
|---|---|---|
| 5.2 and 5.6 | 4 | ended in 2011 and 2018 |
| 7.0, 7.1 and 7.3 | 9 | ended 2019–2021 |
| 7.4 | 7 | ended 28 November 2022 |
| 8.1 | 6 | ended 31 December 2025 |
| Past end of life | 26 (51%) | none |
| 8.2 | 4 | until 31 December 2026 – six weeks left |
| 8.3, 8.4 and 8.5 | 21 | until the end of 2027, 2028 and 2029 |
This is not a random sample, and the headline number should not be read as “half of all shops”. We only see servers that announce their version, and a server nobody configured is more likely to be a server nobody updates. What the number does say: among the shops where the version is public, an attacker reading the same header finds a closed branch every second time.
The wider picture comes from WordPress.org, which collects the PHP version from every install that checks for updates. As of 18 November 2026, 31.7% of WordPress sites run PHP 8.1 or older – all past end of life – and another 22.4% run 8.2, which closes at the end of this year. WordPress itself recommends PHP 8.3 or greater.
One detail from our own data: between the first scan and the re-check, one shop moved from 7.4 to 8.3. It can be done on a live shop.
What “end of life” actually means
A PHP branch gets two years of bug fixes and then two years of security fixes only. After that the branch is closed: when a vulnerability is found, the fix ships for newer branches and the description is public.
| Branch | Released | Security fixes until |
|---|---|---|
| 8.1 | November 2021 | 31 December 2025 (ended) |
| 8.2 | December 2022 | 31 December 2026 |
| 8.3 | November 2023 | 31 December 2027 |
| 8.4 | November 2024 | 31 December 2028 |
| 8.5 | November 2025 | 31 December 2029 |
Source: php.net/supported-versions.php.
For a client, the risk argument is rarely the one that lands. These three usually do:
- Updates silently stop. WordPress core and plugins raise their minimum PHP version. On an old branch the dashboard simply does not offer the new plugin release – including the one that patches a hole in the plugin itself. The site looks up to date and is not.
- The shop is slower than it needs to be. Each branch runs the same code faster; the jump from 5.6 to 7 was the largest. It shows most in the cart and checkout, where page caching does not help.
- The host will switch it for them. Hosting companies retire old branches after a few warning e-mails to the account owner. A forced switch on a day the host picked is the worst way to upgrade.
A fair caveat: some hosts and Linux distributions backport security fixes to older branches, sometimes as a paid service. A version number alone does not prove a site is vulnerable. If you do not know for certain that the host does this, assume it does not.
Check every site you maintain
From the outside, the same way we did it:
curl -sI https://example-shop.com/ | grep -i x-powered-by
For a client list, one URL per line in sites.txt:
#!/usr/bin/env bash
# usage: ./check.sh sites.txt (one URL per line)
while read -r site; do
[ -z "$site" ] && continue
v=$(curl -sI -m 15 "$site" | tr -d '\r' \
| awk -F'PHP/' 'tolower($0) ~ /^x-powered-by:.*php\// {print $2; exit}')
echo "$site ${v:-not advertised}"
done < "${1:-sites.txt}"
A line such as https://example-shop.com/ 7.4.33 means the version is public. not advertised only means the server keeps it to itself – then the version has to be read on the inside: Tools → Site Health → Info → Server in WordPress, Advanced Parameters → Information in PrestaShop, or the PHP selector in the hosting panel.
One method to avoid: uploading an info.php with phpinfo(). It shows the version and the entire server configuration, and it tends to stay there for years. It is one of the two most common exposed files in our scans, and of the eight shops we told about theirs, one removed it.
An upgrade order that does not break the shop
Switching the PHP branch in a hosting panel takes a minute and can be undone in a minute. The risk is not the switch; it is old plugins, themes and custom code that throw on the new branch. So the order matters:
- Take a backup of files and database and confirm it downloads. (What a usable backup contains: Website backup: what you really have.)
- Update core, plugins and theme first, still on the old branch. Current releases are written for current PHP; old ones often are not.
- Remove what is not used. A deactivated five-year-old plugin is the most common cause of a fatal error after the switch.
- Do it on a staging copy if there is one, and move one or two branches at a time rather than from 7.4 straight to the newest. Target a branch with at least a year of fixes ahead: today 8.3 or 8.4.
- Walk the customer path: home page, product, cart, a test order up to the payment step, contact form, admin login. White screen or “critical error” – switch back in the panel and find the culprit in the error log.
- Read the error log for two days.
Deprecatednotices are a to-do list, not an outage;Fatal erroris an outage.
Where custom code usually breaks: functions removed in PHP 8.0 (create_function(), each()), passing null to built-in functions that expect a string (deprecated since 8.1) and dynamic properties (deprecated since 8.2). A static compatibility check before the switch finds most of these without touching production.
If the honest answer is “it cannot be upgraded because the theme will not run”, that is worth saying to the client in exactly those words. It is a debt that grows every year, and it is easier to quote a theme replacement now than to explain a forced switch by the host later.
Then hide the version
X-Powered-By helps nobody. expose_php = Off in php.ini (a toggle in many hosting panels) removes it. That is housekeeping, not a fix – hiding the number does not replace the upgrade – but there is no reason to hand it to every scanner that asks.
Make it part of handover
None of the 26 shops chose to run closed PHP. Somebody launched the site on the branch that was current that year, and nobody was asked to look again. Two lines in a handover document change that: which PHP branch the site runs, and the date its security fixes end. Put the date in a calendar – yours, if you sell maintenance, or the client's, if you do not.
Check a site now
The free Webskan quick scan runs Lighthouse, security headers, basic SEO checks and a probe for files that should not be public – info.php included – on any public site. No sign-up; results in about 30 seconds.
Shipping sites with a coding agent? Give it the Webskan MCP server – free for 2 whole-site audits a day, Developer plan for 30. The whole-site audit reports headers that leak software versions.
Method and caveats
- 547 shops are the home pages that answered correctly in our November 2026 scans; the lists were compiled by hand, by niche, without large chains.
- In the first scan 61 shops sent a PHP version. On 17 November we re-requested each home page once: 51 still sent a version (these are counted), 9 did not answer us that day, 1 had stopped sending the header. On 18 November 49 of the 51 sent the same version again; one answered without the header and one refused the request.
- We count the number in
X-Powered-By. We did not test whether a given server carries backported security fixes. - Support dates: php.net. WordPress shares: public WordPress.org statistics on 18 November 2026 (sum of 8.1 and older). Shops are not named.