HackSpotby Amethyst Apps
How it worksWhat we checkPricingGuidesInsightsAbout
Log inCheck my website
HackSpot / Insights

Old PHP versions past end of life: why they matter now

PHP 8.1 and older got no official PHP2Shell release. End-of-life dates for every branch, what backports cover and how to plan your upgrade.

By HackSpot team (Amethyst Apps) · October 23, 2026 · 4 min read

HackSpot: old PHP versions past end of life and PHP2Shell

The short version: when the PHP project fixed PHP2Shell on 21 October 2026, it released new versions only for PHP 8.2, 8.3, 8.4 and 8.5. Sites on PHP 8.1, 8.0, 7.x or older got no new official release. If your website is on one of those, ask your host what they've done about it and plan a move to a supported version soon. Check what your site shows for free.

End-of-life dates, from php.net

BranchSecurity support endedLast official release
5.631 December 20185.6.40
7.010 January 20197.0.33
7.11 December 20197.1.33
7.230 November 20207.2.34
7.36 December 20217.3.33
7.428 November 20227.4.33
8.026 November 20238.0.30
8.131 December 20258.1.34

And the branches that are still supported:

BranchSecurity support untilPHP2Shell fix
8.231 December 20268.2.35
8.331 December 20278.3.36
8.431 December 20288.4.27
8.531 December 20298.5.12

Note that PHP 8.2 itself reaches end of life on 31 December 2026, about ten weeks after the PHP2Shell fixes. If you're moving anyway, 8.3 or 8.4 buys more time.

Why end of life matters now

"End of life" means the PHP project no longer publishes fixes for that branch. For years many small business sites have run happily on PHP 7.4 or 8.0, because nothing forced a change. PHP2Shell is the kind of event that changes that:

  • The flaws are critical (9.2 out of 10), need no login, and the PHP advisory says they affect all PHP installations serving web requests.
  • Wiz, the company that found them, says every PHP version released in the last decade is affected by at least one of the two flaws.
  • There's no new official release for 8.1 and older.

What about backports?

Because of the severity, the PHP security team published minimal source backports for PHP 7.4, 8.0 and 8.1. These are code changes for people who build PHP themselves, not ready-made releases. Some Linux distributions and long-term support vendors also ship their own fixed packages for older branches.

So a site on PHP 7.4 may have been fixed by its host. You can't tell from the outside, which is why HackSpot says "ask your host" rather than "vulnerable". But even with a backport, an end-of-life branch won't get fixes for the next problem. Treat a backport as time to plan the move, not as the solution.

How to plan the move

  1. Find out what you're on. See how to check which PHP version your website runs.
  2. Ask your host two questions: have you applied the PHP2Shell fixes to our current version, and which supported versions can we move to?
  3. Check your software. WordPress recommends PHP 8.3 or newer. Old plugins, themes and custom code are the usual reason a site breaks after an upgrade.
  4. Test on a copy first, then switch the live site. Our cPanel and Plesk guide walks through it.
  5. Put the next date in your diary. Every branch has an end date; knowing yours avoids a scramble next time.

If your developer says "the site won't work on newer PHP"

That's a common and honest answer for older sites. It usually means some code needs updating. Ask for an estimate. The cost of updating is normally far smaller than the cost of a compromised site, and staying on an unsupported branch only gets riskier.

Questions people ask

Is PHP 7.4 still safe to use?

The PHP project stopped supporting PHP 7.4 on 28 November 2022. It received a minimal source backport for PHP2Shell, but no new official release. Ask your host whether they've applied a fix and plan to move to a supported version.

Is PHP 8.1 affected by PHP2Shell?

Yes, older branches are affected. PHP 8.1 reached end of life on 31 December 2025, so there's no new official release; your host may have applied a backported fix.

When does PHP 8.2 reach end of life?

On 31 December 2026, according to php.net. It received the PHP2Shell fix in 8.2.35.

Which PHP version should a small business use?

A supported branch your website works with. For most sites in late 2026, PHP 8.3 or 8.4 is a sensible choice.

Can HackSpot tell me when my PHP is getting old?

Yes. A free check shows the PHP version your site reveals, and HackSpot's monitoring flags end-of-life branches in plain language.

More on PHP2Shell

  • CVE-2026-109618 and CVE-2026-109619 explained in plain English
  • How to update PHP in cPanel and Plesk
  • What to ask your web host (email template)
  • PHP2Shell: what small businesses need to do today

Sources

  • Unsupported branches (php.net)
  • Supported versions (php.net)
  • PHP security advisory, 21 October 2026 (php.net)
  • PHP 8.2.35 release announcement (php.net)
  • PHP2Shell research (Wiz)
  • WordPress requirements (WordPress.org)

Check your website free

See what your website shows the world in about a minute: a plain-language report, who should fix each thing, and a message to send them.

Check my website

Free to check

See what your website shows the world.

Check my website free
HackSpotby Amethyst Apps

Plain-language security checks for your website and the suppliers your business depends on.

HackSpot

  • How it works
  • What we check
  • Free check
  • Pricing

Resources

  • Guides
  • Insights
  • Supplier status

Help

  • About
  • Security
  • Contact us

Amethyst Apps

  • All apps
  • IndexStream
  • Partners

© 2026 Amethyst Apps. Built in the UK.

2G, Ingram House, 227 Ingram Street, Glasgow, G1 1DA, United Kingdom

PrivacyTermsCookiesSecuritySitemapPartners
EnglishEspañolFrançaisDeutschItalianoPortuguêsNederlandsPolskiSvenska日本語
HackSpot