Skip to content

PHP 8.2 end of life: plan the move to 8.3 or 8.4

Plan your move off PHP 8.2 before its end of life on 31 December 2026, the date after which php.net ships no more security fixes for it. You will find every WordPress site, cPanel account and Composer app still on 8.2, choose between PHP 8.3 and 8.4, and work a timeline backwards from the deadline.

If your WordPress sites, cPanel server or Composer application still run PHP 8.2, this plan gets you off it before 31 December 2026, the day php.net stops fixing it. It is for site owners, agencies and server administrators who checked their PHP version after the “PHP2Shell” advisory of 21 October 2026 and found 8.2, for years the default on shared hosting. Move to PHP 8.4 unless a plugin, theme or package you cannot replace fails on it; then take 8.3, which php.net supports until the end of 2027. End of life (EOL) means the PHP project ships no fix for 8.2 when the next serious bug lands, which is what happened to PHP 8.1 on 21 October. A Composer application is a PHP app whose libraries are installed by Composer, the PHP package manager.

What you’ll accomplish

  • A dated list of every site, cPanel account and application still on PHP 8.2, read from the web handler, not only the command line.
  • A choice between 8.3, 8.4 and 8.5 made against written criteria.
  • A timeline that works backwards from 31 December 2026, with production moved before the mid-December change freeze.
  • A rollback window during which going back to 8.2 is still safe, then a date when 8.2 leaves the server.
  • A plain answer for the sites that cannot make the date.

Prerequisites

  • WordPress 6.7 or newer for PHP 8.4, and 6.9 or newer for 8.5, per the core handbook as of 27 October 2026 (PHP compatibility and WordPress versions). The requirements page recommends PHP 8.3 or greater (WordPress requirements).
  • On cPanel, root access to WHM (WebHost Manager, the server-wide admin side of cPanel) or a reseller login with the MultiPHP Manager feature. EasyApache 4 release 25.91 of 21 October 2026 ships ea-php83 8.3.36, ea-php84 8.4.27 and ea-php85 8.5.12 (EasyApache 4 change log).
  • On a plain Linux server, root access and a package source that offers 8.3 or 8.4.
  • A staging copy of each important site, and a recent backup you have restored at least once.

How it works

Each PHP branch gets two years of active support, with bugs and security issues fixed in regular point releases, then two more years of security fixes only (php.net supported versions). After that it is end of life. As of 27 October 2026, php.net gives these dates:

BranchActive support untilSecurity fixes until
8.231 Dec 2024 (over)31 Dec 2026
8.331 Dec 2025 (over)31 Dec 2027
8.431 Dec 202631 Dec 2028
8.531 Dec 202731 Dec 2029

So 8.2 has been security-only for almost two years, and 31 December 2026 is its last possible fix date. The 8.2.35 announcement of 21 October 2026 says it plainly: “PHP 8.2 reaches end of life on 31 December 2026 and will receive no further security fixes after that date” (php.net 2026 archive).

The same day showed what that means. The two critical bugs nicknamed “PHP2Shell”, CVE-2026-109618 and CVE-2026-109619, let an unauthenticated visitor run code on the server. Their fixes shipped as 8.2.35, 8.3.36, 8.4.27 and 8.5.12. For 8.1 there was no release, because “PHP 8.1 and older no longer receive updates from the PHP project”. Anyone on 8.1 waited for a vendor backport, a patch applied to the old version by a distribution or hosting vendor. From 1 January 2027, 8.2 is in that position.

Vertical timeline from late October to January: inventory by 6 November, staging tests by 27 November, production moved by 11 December, rollback window to 24 December, the last 8.2 security fix on 31 December, then the first 2027 advisory with fixes for 8.3 to 8.5 and a red dead end for anything still on 8.2

Which version: 8.3, 8.4 or 8.5

Pick 8.4 by default. It gets security fixes until the end of 2028, WordPress has supported it since 6.7, and plugin authors have had almost two years with it. Pick 8.3 only when a plugin, theme or package you cannot replace fails on 8.4. That buys one year, because 8.3 reaches end of life on 31 December 2027. Pick 8.5 when staging passes clean on it and you want the longest runway; it is also the branch plugin authors have had the least time with. PHP 8.6 is at release candidate 4 in the php.net archive for October 2026, and php.net asks that it not be used in production.

CriterionPHP 8.3PHP 8.4PHP 8.5
Security fixes until (php.net, 27 Oct 2026)31 Dec 202731 Dec 202831 Dec 2029
Bug fixes (active support)Ended 31 Dec 2025Until 31 Dec 2026Until 31 Dec 2027
WordPress core support (handbook, 27 Oct 2026)6.4 and newer6.7 and newer6.9 and newer
cPanel package (EA4 25.91)ea-php83, 8.3.36ea-php84, 8.4.27ea-php85, 8.5.12
Jump from 8.2One year of deprecationsTwo yearsThree years, least plugin testing
Next forced moveEnd of 2027End of 2028End of 2029

An agency with dozens of client sites gets the most from 8.4: one compatibility pass covers two more years. A shop with one old payment plugin that only declares 8.3 support takes 8.3 now and books the replacement for 2027. The deprecations are listed in Migrating from PHP 8.3.x to PHP 8.4.x.

The timeline, backwards from 31 December

Count back from the deadline, not forward from today. The last two weeks of December are a change freeze for most businesses, the period when nobody touches production, so production moves before it.

DatesMilestoneDone when
27 Oct to 6 NovInventoryEvery site and account has a version next to it
9 Nov to 27 NovCompatibility test on stagingEach site passed on the target, or has a written blocker
30 Nov to 11 DecMove productionA few sites per day, off-peak; 8.2 stays installed
14 Dec to 24 DecRollback window8.2 still gets fixes, so switching a site back is safe
31 DecLast day of 8.2 security fixesNothing on 8.2 except dated exceptions
First January windowRemove 8.2ea-php82 or the php8.2 packages are uninstalled

If you read this later than 27 October, compress the first two rows, not the last three.

Step-by-step

  1. Read the version from WordPress, on the web side. In the WordPress admin open Tools » Site Health » Info and expand Server. The row PHP version shows the version that served the page, for example 8.2.35 (Supports 64bit values). Record it per site; this is the PHP that handles visitors.

  2. Read the version from WP-CLI, which may differ. WP-CLI is the wp command that manages WordPress from a shell. On the server, inside the site directory:

    wp cli info

    Example output (abridged):

    PHP binary:     /opt/cpanel/ea-php82/root/usr/bin/php
    PHP version:    8.2.35
    php.ini used:   /opt/cpanel/ea-php82/root/etc/php.ini
    WP-CLI version: 2.12.0

    For a one-line answer:

    wp --skip-plugins --skip-themes eval 'echo PHP_VERSION . PHP_EOL;'

    Example output:

    8.2.35

    This is the command-line PHP, the one cron jobs use. PATH picks it, not the site’s web setting, so it can say 8.2 while visitors get 8.4. If the two disagree, note both. PHP CLI on cPanel running a different version than PHP-FPM has the fix, and how to check which PHP version your site really runs covers the web side.

  3. On cPanel, read the system default and every domain in one pass. The system default is the version every account inherits unless it chose one:

    whmapi1 php_get_system_default_version

    Example output:

    ---
    data:
      version: ea-php82
    metadata:
      command: php_get_system_default_version
      reason: OK
      result: 1
      version: 1

    Then list every virtual host, count the versions and print the ones on 8.2 with their source:

    whmapi1 --output=json php_get_vhost_versions | python3 -c '
    import json, sys, collections
    rows = json.load(sys.stdin)["data"]["versions"]
    print(collections.Counter(r["version"] for r in rows))
    for r in rows:
        if r["version"] == "ea-php82":
            src = "system default" if r["phpversion_source"].get("system_default") else "set on domain"
            print(r["vhost"], r["account"], src, "fpm" if r["php_fpm"] else "no-fpm")
    '

    Example output:

    Counter({'ea-php82': 23, 'ea-php83': 9, 'ea-php84': 5})
    boutique-lac.com boutique system default fpm
    agence-nord.ca agence set on domain fpm
    clinique-rive.qc.ca clinique system default no-fpm

    The same list is in WHM » Software » MultiPHP Manager. Rows marked system default all change together when you change the default in step 7, so count them separately. Rows marked set on domain move one at a time.

  4. On a plain Linux server, read the installed versions and each site’s handler. Each site hands PHP requests to a PHP-FPM socket, and the socket name carries the version. FPM is the FastCGI Process Manager, the pool of PHP workers behind nginx or Apache. On Debian or Ubuntu:

    ls /etc/php/
    grep -rh 'fastcgi_pass\|SetHandler' /etc/nginx/sites-enabled/ /etc/apache2/sites-enabled/ 2>/dev/null | sort | uniq -c

    Example output:

    8.2  8.4
          7 	fastcgi_pass unix:/run/php/php8.2-fpm.sock;
          2 	fastcgi_pass unix:/run/php/php8.4-fpm.sock;

    Each php8.2-fpm.sock line is a site to move. As of 27 October 2026, Ubuntu’s CVE tracker lists php8.2 as “Not in release” for every LTS from 20.04 to 26.04. On an LTS, PHP 8.2 came from a PPA (a personal package archive, a repository outside Ubuntu’s own), and it is the PPA owner, not Ubuntu, who decides whether it gets patched.

  5. Check Composer applications for a blocker. In the application directory:

    composer why-not php 8.4

    Example output when something blocks:

    acme/legacy-pdf  2.3.1  requires  php (~8.1.0 || ~8.2.0 || ~8.3.0)

    Example output when nothing does:

    There is no installed package depending on "php" in versions not matching 8.4

    A "php": "^8.2" requirement in composer.json already allows 8.4. The usual trap is config.platform.php pinned to 8.2.0, which makes Composer resolve as if the server were 8.2. Raise it to the target before you run composer update.

  6. Test each site on the target version, on staging. Three existing articles cover the test loop, so pick the one that matches the site. For WordPress on cPanel, start with WordPress compatibility check before a PHP version bump. The staging vhost method in move WordPress to PHP 8.5 on cPanel with a real compatibility test loop works unchanged with ea-php84 as the target. For a custom application, use the PHPStan and Rector pass and the parallel PHP-FPM pool in upgrading a production app to PHP 8.4 without downtime surprises. Write the result next to each site: passed, passed with deprecation notices, or blocked by a named plugin.

  7. Move production in small batches. On cPanel, per domain:

    whmapi1 php_set_vhost_versions version=ea-php84 vhost=boutique-lac.com

    Expected: result: 1 and reason: OK in the metadata block. When only system default rows remain, and every one of them has passed step 6, change the default in one deliberate step:

    whmapi1 php_set_system_default_version version=ea-php84

    On a plain server, point the site’s fastcgi_pass or SetHandler line at the new socket and reload the web server, as in the parallel-pool article. Leave the 8.2 packages installed until step 9.

  8. Keep the rollback window open until 24 December. During it, 8.2 still receives security fixes, so moving a site back with version=ea-php82 is a one-line decision with no security cost. Watch each moved site’s error log for PHP Fatal error lines; PHP Deprecated lines are not a reason to roll back.

  9. Remove 8.2 in the first January window. Once no domain resolves to it, uninstall ea-php82 in WHM » Software » EasyApache 4, or run apt remove 'php8.2-*' on Debian and Ubuntu. A version that is not installed cannot be selected by mistake.

Validate it works

  1. Run the count from step 3 again. The expected result has no ea-php82 entry:

    Counter({'ea-php84': 32, 'ea-php83': 5})
  2. Open Site Health » Info » Server on three sites you moved. PHP version must read 8.4.27 or newer.

  3. Run wp cli info once per account. PHP version must match the web version, or that account’s cron jobs run on a PHP you are about to remove.

  4. Confirm the workers run under the new version:

    systemctl list-units --plain --no-legend 'ea-php*php-fpm*'

    Example output:

    ea-php83-php-fpm.service  loaded active running  The PHP FastCGI Process Manager
    ea-php84-php-fpm.service  loaded active running  The PHP FastCGI Process Manager

    No ea-php82-php-fpm.service line should remain after step 9.

  5. Place a test order and submit a form on each moved site. A fatal error in the log is a rollback; a deprecation notice is not.

Troubleshooting

  • Site Health shows 8.4 but a scheduled task fails with an 8.2 error. The cron job runs the command-line PHP from PATH. Call the binary by its full path in the cron line, for example /opt/cpanel/ea-php84/root/usr/bin/php, or fix the account PATH as in the article linked in step 2.
  • php_set_vhost_versions answers that the version is not installed. ea-php84 is not provisioned yet. Add it in WHM » Software » EasyApache 4 under the current profile, then rerun the command.
  • One domain still serves 8.2 after the switch. Look for a handler line in the site’s .htaccess, such as AddHandler application/x-httpd-ea-php82, often copied from another site. Remove that block; MultiPHP Manager writes its own.
  • A plugin fails only on 8.4 with Fatal error: Uncaught TypeError. That plugin is the blocker. Record it, move the site to 8.3 for now, and open a dated task to replace the plugin before 31 December 2027.

If you cannot make the date

Some sites will miss it: a plugin with no 8.3 release, a client who will not approve a change in December, an application nobody can rebuild in time. Treat each as a named exception with an owner and a January date, not as a silent default.

Paid extended support exists. As of 27 October 2026, cPanel documents TuxCare Extended Lifecycle Support (ELS) for PHP, vendor-patched packages for end-of-life versions that appear in MultiPHP Manager (cPanel documentation). That page defers to TuxCare’s own list for the versions covered, so check whether PHP 8.2 is on it before you count on it. Ubuntu Pro covers packages in Ubuntu’s own LTS archives, and php8.2 is in none of them, so a PPA build gets no Pro coverage. Until each exception moves, keep the settings from PHP2Shell mitigations until you can patch in place, because the next advisory will arrive with no 8.2 release behind it.

When this is the wrong approach

If you rent one account on someone else’s server, you do not need the timeline. Open MultiPHP Manager in cPanel, test on a staging copy, and pick 8.4. If your sites already run 8.3 or newer, nothing here applies until the autumn of 2027. If you are still on PHP 8.1 or older, the deadline has already passed. Start with PHP 7.4, 8.0 or 8.1: how to get the PHP2Shell fix, then migrating PHP 7.x applications to PHP 8.x. For a whole cPanel fleet with customer communication and per-account rollback, see server-wide migration off an EOL PHP version on cPanel.

Running WordPress that earns real money deserves an operator — Stack Harbor runs that stack under Enterprise WordPress; book an infrastructure consult.