Skip to content

PHP 8.2 end of life: what to do before December 31, 2026

PHP 8.2 stops getting security fixes on December 31, 2026. Here's what that means for your site, which version to pick and a week-by-week plan to switch in time.

PHP 8.2 end of life is December 31, 2026. After that date, the PHP project stops releasing security fixes for the 8.2 branch, so any new flaw found in it stays open unless your host or a paid vendor patches it. Your website won't switch off on January 1, but it will run on software the PHP project no longer maintains.

The fix is to move to a supported version before then: PHP 8.4 for most WordPress sites, 8.3 if a key plugin isn't ready, or 8.5 if everything you run supports it. You have about 9 weeks, which is enough time to test properly if you start this week.

Do this in 5 minutes: check your PHP version in WordPress under Tools, then Site Health, then Info, then Server. If it starts with 8.2 or lower, pick a switch date and ask your host one question: what happens to sites still on 8.2 after December 31?

What PHP 8.2 end of life means

PHP is the programming language that runs WordPress, WooCommerce and Laravel, and each version has a fixed lifespan. php.net's supported versions page explains that each branch is fully supported for 2 years from its release, then gets 2 more years of fixes for critical security issues only. After that it reaches end of life, and php.net says users "should upgrade as soon as possible, as they may be exposed to unpatched security vulnerabilities."

  • Active support ended December 31, 2024. Since then, 8.2 has only received security releases.
  • PHP 8.2 security support ends December 31, 2026. The PHP 8.2.35 release notes say 8.2 "will receive no further security fixes after that date."
  • Nothing breaks on January 1. Your site keeps working. What changes is that the next serious PHP bug won't get an 8.2 fix from the PHP project.

Plenty of sites are in this spot. W3Techs data from October 27, 2026 shows 8.2 on 27.4% of websites that use PHP 8, second only to 8.3.

PHP supported versions and dates

These are the PHP supported versions as listed on php.net today:

VersionReleasedActive support untilSecurity fixes until
PHP 8.2Dec 8, 2022Dec 31, 2024 (ended)Dec 31, 2026
PHP 8.3Nov 23, 2023Dec 31, 2025 (ended)Dec 31, 2027
PHP 8.4Nov 21, 2024Dec 31, 2026Dec 31, 2028
PHP 8.5Nov 20, 2025Dec 31, 2027Dec 31, 2029
PHP 8.6Scheduled Nov 19, 2026Not listed yetNot listed yet

The PHP 8.6 release date is November 19, 2026, according to the PHP 8.6 release schedule. php.net released the fourth release candidate on October 21 and asks people not to use it in production. Its support dates aren't on php.net's table yet.

PHP 8.1, for comparison, reached end of life on December 31, 2025, according to php.net's unsupported branches page. That date matters for the next section.

Not sure what is costing you leads?

Send your website and we will record a free 2 minute video showing the 3 fixes we would make first.

Get my free video audit

Why PHP 8.2 end of life matters more after php2shell

On October 21, 2026, PHP fixed the php2shell vulnerability, 2 critical flaws that can let an attacker run code on a web server without logging in. How that release played out shows exactly what end of life means:

  • PHP 8.2 got a fix. PHP 8.2.35 shipped the same day as the fixes for 8.3, 8.4 and 8.5, because 8.2 was still inside its security window.
  • PHP 8.1 didn't. php.net's security advisory says 8.1 and older "no longer receive updates from the PHP project." There were only minimal source patches that a server admin would have to build, plus backports from some vendors.
  • CISA told organizations to take 8.1 and older offline until patched or updated. That's in its php2shell alert, and CISA has since listed both flaws as exploited in real attacks.

From January 1, 2027, PHP 8.2 is where 8.1 was this October. If a bug of that size turns up next year, no 8.2 release is coming.

Before you plan the upgrade, make sure your 8.2 site has the php2shell fix today: 8.2.35, or a patched build your host confirms in writing.

Which PHP version to move to

Here's what the official requirements say:

  • WordPress.org recommends PHP 8.3 or greater. Its hosting handbook goes further: "PHP 8.4 or later is recommended for production environments." It lists 8.4 as fully supported by WordPress 6.7 and later, and 8.5 by WordPress 6.9 and later.
  • WooCommerce asks for PHP 8.3 or greater, tested up to PHP 8.4.
  • Laravel 13 requires PHP 8.3 or newer. Laravel 12 runs on 8.2 to 8.5 and gets security fixes until February 24, 2027.

How to choose the best PHP version for WordPress and your plugins:

  • PHP 8.4: the default pick. It matches the handbook's advice, WooCommerce is tested on it, and it gets security fixes until December 31, 2028.
  • PHP 8.3: only if a plugin, theme or app you can't replace isn't ready for 8.4. Its security fixes end December 31, 2027, so you'll repeat this project next year.
  • PHP 8.5: if every plugin and theme you use supports it. Security fixes run until December 31, 2029, but note that WooCommerce lists testing only up to 8.4.
  • PHP 8.6: not for this deadline. It ships November 19, and plugins and themes will need time to catch up.

Going from 8.2 to 8.4 skips a version, and each PHP release removes or changes some older features, as php.net's migration guide for 8.4 shows. That's why old, unmaintained plugins are the usual source of trouble, and why the plan below starts with testing.

A 9-week upgrade plan to December 31

There are 9 weeks between now and the deadline. This plan leaves room for testing, the holidays and a buffer week.

WeekDatesWhat to do
1Oct 27 to Nov 1Confirm the php2shell fix. Take a full backup. List every site and copy on your account with its PHP version, plugins and theme.
2Nov 2 to 8Check each plugin and theme: when was it last updated, and does the developer mention PHP 8.3 or 8.4? Pick your target version.
3Nov 9 to 15Make a staging copy. Update WordPress, plugins and theme there, then switch staging to the new PHP version.
4Nov 16 to 22Test staging: forms, booking, checkout, payments, logins, search. Fix or replace what breaks. Apply the same plugin and theme updates on the live site.
5Nov 23 to 29Service businesses: switch the live site early in the week. Stores: freeze changes through Black Friday (Nov 27).
6Nov 30 to Dec 6Stores: switch after Cyber Monday (Nov 30). Everyone: watch the site closely.
7 and 8Dec 7 to 20Monitor the error log, Site Health, form submissions and orders. Fix stragglers.
9Dec 21 to 31Buffer. Confirm nothing on your account still runs 8.2, including old staging copies and subdomains.

On switch day, work through this list in order:

  1. Take a fresh backup of files and database.
  2. Change the PHP version in your hosting panel at a quiet time. Our guide on how to update the PHP version in WordPress has the steps for each panel.
  3. Right away, test the pages and forms that bring you calls, leads and orders, on desktop and phone.
  4. Know your way back. Hostinger's help page, for example, says you can only switch back to an older version within the same login session, so test before you log out.
  5. If you see "There has been a critical error on this website," read how to fix a WordPress critical error after a PHP update.

On staging, turn on WordPress debug logging to catch warnings. Keep it off on the live site, since Site Health warns that a debug log can end up in a publicly reachable file.

What hosts do with end-of-life PHP versions

Hosts handle end of life differently, and some act before PHP's own date. Three published examples:

  • Hostinger says PHP versions below 8.2 "are deprecated and are no longer available for selection." Sites already on them keep running and can only move up. Its help page doesn't yet say what happens to 8.2 after December 31.
  • Acquia ended PHP 8.2 support on October 1, 2026, 3 months early, and upgrades environments still on 8.2 to PHP 8.4 automatically.
  • cPanel servers can add TuxCare Extended Lifecycle Support, a licensed extension that keeps patching old PHP versions, with critical and high-severity fixes within 14 days of disclosure.

That gives 3 likely outcomes: your host upgrades you on its own schedule, leaves you on an unpatched version, or sells extended support. Ask your host which one applies, and get the date in writing. Paid extended support can cover a site that truly can't move yet, but it's a bridge, not a plan.

What to do next

This week, confirm your site has the php2shell fix, check your PHP version and ask your host about its 8.2 plans. Then book the staging test for early November, so the live switch happens with weeks to spare.

If you'd rather hand it off, we build and maintain WordPress and Laravel sites and can run the test and the switch for you. Or start with a free 2 minute video audit of your site, showing the 3 fixes we'd make first.

Common questions

Will my website stop working when PHP 8.2 reaches end of life?

No. Your site keeps running on January 1, 2027. What stops is security fixes from the PHP project, so any new flaw found in 8.2 stays open. Your host may also act on its own schedule: some remove old versions from their menus, and some upgrade sites automatically. Ask your host what it plans to do and when.

Is it safe to stay on PHP 8.2 until December 31?

Only on the patched release. PHP 8.2.35, released October 21, 2026, fixes the php2shell flaws, and 8.2 keeps getting security fixes until December 31. Confirm with your host that your site runs 8.2.35 or a patched build. Then use the remaining weeks to test and switch, rather than waiting for the last days of December.

Should I upgrade from PHP 8.2 to 8.3 or 8.4?

For most WordPress sites, 8.4. The WordPress hosting handbook recommends 8.4 or later for production, WooCommerce is tested up to 8.4, and 8.4 gets security fixes until December 31, 2028. Choose 8.3 only if something you rely on isn't ready for 8.4, knowing its security support ends December 31, 2027.

Should I wait for PHP 8.6?

No. PHP 8.6 is scheduled for November 19, 2026, which leaves little time before the 8.2 deadline, and plugins and themes need time to support a new version. php.net says not to run its release candidates in production. Move to 8.4 now, and consider 8.6 later once your plugins and theme support it.

What if a plugin doesn't work on PHP 8.3 or newer?

First, update it and check for a fix from its developer. If it's abandoned, replace it with a maintained plugin that does the same job, and test the replacement on staging. As a last resort, paid extended support for old PHP versions can buy time, but it only delays the decision, so set a date to replace the plugin.

Get your free video audit

The 3 fixes we'd make first on your site, within 1 business day.

Send my website
Free video auditWhatsApp