The PHP 8.2 end-of-life date is December 31, 2026, when the PHP project stops shipping security fixes for the 8.2 branch. That is about six weeks from today. Any WordPress, Drupal or custom PHP site still on 8.2 after that date runs on a version nobody patches.
Our Q4 2026 platform calendar already lists the date. This post is the practical part: how to find which PHP version a site runs, what each major host says it will do, which version to move to, how to test it on staging, and what tends to break.
The short version: check every client site this week. Move to PHP 8.3 or 8.4, test on a staging copy with error logging on, and read your host’s own retirement date. For some hosts, the PHP 8.2 end-of-life cutoff comes before December 31. Current WordPress and Drupal releases both run on 8.3 and 8.4.
PHP2Shell update: PHP2Shell, two critical PHP flaws that can allow unauthenticated remote code execution, was patched on October 21, 2026 in PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12. Sites on PHP 8.1 or older got no upstream release and depend on a host or vendor backport. See our PHP2Shell coverage for what to check.
What the PHP 8.2 end-of-life date means
PHP gives each branch two years of active support and then two years of security fixes only. The PHP supported versions page lists these dates as of October 2026:
| Branch | Released | Active support until | Security fixes until |
|---|---|---|---|
| PHP 8.2 | Dec 8, 2022 | Dec 31, 2024 | Dec 31, 2026 |
| PHP 8.3 | Nov 23, 2023 | Dec 31, 2025 | Dec 31, 2027 |
| PHP 8.4 | Nov 21, 2024 | Dec 31, 2026 | Dec 31, 2028 |
| PHP 8.5 | Nov 20, 2025 | Dec 31, 2027 | Dec 31, 2029 |
Two other dates sit close by. PHP 8.4 leaves active support on December 31 and moves to security fixes only. And PHP 8.6 is planned for general availability on November 19, according to the PHP 8.6 release schedule. We covered what is in it in what is shipping in PHP 8.6.
PHP’s own wording on end of life is plain. Users of an end-of-life branch "should upgrade as soon as possible, as they may be exposed to unpatched security vulnerabilities."
How to find which PHP version a site runs
Start with an inventory. You need the PHP version for every production site, and for staging too, since they can differ.
WordPress. Go to Tools, then Site Health, then the Info tab. Open the Server section. "PHP version" is near the top. The Status tab also flags an outdated PHP version as a critical issue. The Site Health documentation describes both tabs.
Drupal. Go to Reports, then Status report, at /admin/reports/status. The general information block shows PHP and its version. For full detail, /admin/reports/status/php shows the PHP information page. Acquia’s support notes describe a case where the two disagreed because a contributed module reported its own minimum. If they differ, trust the PHP information page.
cPanel hosts. Open MultiPHP Manager. It lists each domain and its PHP version. A domain marked "inherit" uses the server’s default version, which only the server administrator controls. To change a domain, tick its checkbox, pick a version from the PHP Version menu and click Apply, per the cPanel MultiPHP Manager docs.
Managed hosts. Each one shows the version in its dashboard. The next section covers where.
PHP 8.2 end-of-life dates at each managed host
This is where PHP 8.2 end-of-life planning gets uneven. Some hosts retire versions early, some upgrade sites for you, and some publish no date at all. Here is what each host’s own documentation said as of October 2026.
| Host | Where to switch | PHP 8.2 status in its docs |
|---|---|---|
| Acquia Cloud Platform | Cloud Platform UI, PHP settings | Retired October 1, 2026. Applications still on 8.2 were to be upgraded to 8.4 automatically. |
| Pantheon | php_version in pantheon.yml; check under Settings, PHP version |
Listed as fully supported. No removal date. Pantheon promises 90 days’ notice before removing a version. |
| WP Engine | User Portal: Sites, environment, PHP version under Updates | No 8.2 date given. At end of life, WP Engine says it upgrades all sites automatically, and upgrades cannot be deferred. |
| Kinsta | MyKinsta: WordPress Sites, environment, Tools, PHP settings, Change | No 8.2 date given. Policy text says unsupported versions are removed at end of life. |
| SiteGround | Site Tools: Devs, PHP Manager | No 8.2 date given. Sites on Managed PHP get moved forward automatically; manually set versions do not. |
Host details to read before you switch
A few details matter more than the table can show.
Acquia’s PHP 8.2 FAQ says you could not choose the target version for its managed upgrade, and PHP 8.2 can no longer be selected. If an Acquia site jumped from 8.2 to 8.4 in October, test it as an 8.4 site now.
Pantheon’s PHP guide says removed versions get upgraded to the oldest available version. Its upgrade guide covers Multidev and the hotfix caveat.
WP Engine’s PHP upgrade guide includes a PHP Test Driver ("Preview PHP") that lets you browse a site on another version first.
Kinsta’s sources point two ways. Its PHP update guide says it removes unsupported versions at end of life. Its changelog entry, last updated April 2025, says it offers its own free long-term support for some end-of-life releases, 7.4 and 8.0 at the time. Ask Kinsta which applies to 8.2.
SiteGround’s Managed PHP article explains the automatic option. Check whether each client site is on it.
One more data point: WP Cloud, Automattic’s hosting platform, says PHP 8.2 will be removed on December 15, 2026 at 12:00 UTC. That is two weeks before the PHP project’s date. For a full host comparison, see our managed WordPress host buyer’s framework.
Choosing between PHP 8.3 and 8.4 for a CMS site
For most CMS sites, the answer is 8.3 or 8.4. Both are supported by current WordPress and Drupal releases.
WordPress. The core team recommends PHP 8.3 or greater on its requirements page. A May 2026 Make WordPress Core post says WordPress 6.8 and later fully support PHP 8.4, and 6.9 and 7.0 fully support 8.5. The compatibility table marks 8.3, 8.4 and 8.5 as supported for WordPress 7.0 and 7.1.
Drupal. The Drupal PHP requirements page lists PHP 8.3 and 8.4 for Drupal 11.1 and later, with 8.5 added from 11.3. Drupal 10.4 to 10.6 support PHP 8.1 through 8.4, not 8.5.
How we would choose. PHP 8.4 gets security fixes until December 2028, a year longer than 8.3. It also removes more old behavior, so it finds more problems in old plugins. If a site has a lot of older custom code, 8.3 is the smaller step. If the code is current, 8.4 buys an extra year before the next upgrade.
PHP 8.5 is an option for sites already on WordPress 6.9 or later, or Drupal 11.3 or later. Check every plugin and module first. Core support does not mean your add-ons are ready.
Drupal 10 sites and the PHP version question
Drupal 10 sites need extra care. Drupal 10 tops out at PHP 8.4, and Drupal 11 needs at least PHP 8.3. Moving a Drupal 10 site to 8.3 or 8.4 now clears the PHP 8.2 end-of-life deadline and one Drupal 11 requirement at the same time.
If you are planning the Drupal 11 move anyway, do the PHP upgrade first, on Drupal 10. Then run Drupal Upgrade Status and follow our Drupal 10 to 11 upgrade guide. Two smaller changes are easier to test than one large one.
How to test a PHP upgrade on staging
Do not switch production first. A PHP 8.2 end-of-life upgrade is a code change, so treat it like one. The steps below work on any host.
- Copy production to staging. Include the database and uploaded files.
- Update everything on staging first. Core, themes, plugins and modules. Many PHP fixes are already in newer releases.
- Turn on error logging. In WordPress, set
WP_DEBUGandWP_DEBUG_LOGinwp-config.php. Errors then go towp-content/debug.log. In Drupal, check Reports, then Recent log messages, with the Database Logging module on. - Switch staging to the new PHP version. Use the host’s tool from the table above.
- Click through the paths that make money or serve members. Donation, checkout, join and renew, event registration, login, search, forms and any AMS or CRM sync.
- Read the log. Fatal errors block the upgrade. Deprecation notices are a to-do list for later.
- Switch production and watch the log for a day. Keep the old version noted so you can roll back while it is still offered.
The WordPress debugging guide warns against running these debug tools on live sites. Use them on staging only. The same habits apply to the WordPress release cycle; our WordPress 7.2 Beta 1 staging checklist uses a similar order.
What usually breaks in a PHP 8.2 end-of-life upgrade
Most current plugins and modules move from 8.2 to 8.3 or 8.4 without trouble. Problems cluster in old, unmaintained or custom code. These are the changes to look for, from the PHP migration guides.
Dynamic properties. PHP 8.2 itself deprecated creating properties that a class does not declare. Old plugins and themes do this a lot. If your 8.2 logs already show these notices, they will keep showing on 8.3 and 8.4. Neither later migration guide lists a change to that rule, so they are notices, not new failures. They are still worth fixing. The fix is to declare the property, or to add the #[\AllowDynamicProperties] attribute to the class.
Implicitly nullable parameters (8.4). Code like function foo(T1 $a = null) now raises a deprecation notice. The fix is ?T1 $a = null. Old code is full of this pattern, so expect noisy logs.
Removed extensions (8.4). IMAP, OCI8, PDOOCI and PSpell moved out of PHP core to PECL. A plugin that reads a mailbox through `imap*` functions will fail unless the host installs the extension.
Stricter errors (8.4). exit() with an invalid type now throws a TypeError. round() throws a ValueError for an invalid mode. The E_STRICT level is gone and its constant is deprecated.
Changed results (8.3). range() and number_format() behave differently with some inputs. These rarely fail loudly. They can change numbers in reports or exports.
The PHP 8.4 migration guide has the full list, and the 8.3 guide sits beside it.
What happens if you ignore the PHP 8.2 end-of-life date
The site keeps running on January 1. PHP 8.2 does not switch off. What stops is new security fixes. A flaw found in PHP 8.2 after December 31 stays open on your server.
The bigger near-term risk is your host. Acquia set its own cutoff of October 1. WP Engine says it upgrades at end of life and will not defer. WP Cloud removes 8.2 on December 15. A forced upgrade with no staging test can break donation and registration forms during year-end giving season.
Ignoring the PHP 8.2 end-of-life deadline means letting the host pick the date. Picking it yourself costs a staging test.
Frequently Asked Questions
When is the PHP 8.2 end-of-life date?
December 31, 2026. After that date the PHP project publishes no more security fixes for the 8.2 branch, according to its supported versions page.
Will my website stop working after the PHP 8.2 end-of-life date?
No. The site keeps running. It stops getting security fixes for PHP itself, and your host may upgrade it for you on its own schedule.
How do I check my PHP version in WordPress?
Go to Tools, then Site Health, then Info, and open the Server section. The PHP version is listed there.
How do I check my PHP version in Drupal?
Open the status report at /admin/reports/status. For full detail, open /admin/reports/status/php.
Should I move to PHP 8.3 or 8.4?
Both work with current WordPress and Drupal. PHP 8.4 gets security fixes a year longer, until December 2028. PHP 8.3 is the smaller step for sites with a lot of old custom code.
Can a Drupal 10 site run PHP 8.4?
Yes. Drupal 10.4 to 10.6 support PHP 8.1 through 8.4. Drupal 10 itself reaches end of life on December 9, 2026, so plan the Drupal 11 move too.
Should I wait for PHP 8.6?
No. PHP 8.6 is planned for November 19, and CMS support follows later. As of October 2026, Drupal listed 8.6 support as pending. Move to 8.3 or 8.4 now.
What breaks most often after a PHP upgrade?
Old or unmaintained plugins, themes and custom modules. Look for deprecation notices about dynamic properties and nullable parameters, and for code that uses the IMAP extension on PHP 8.4.
Will my host upgrade PHP 8.2 for me?
Some will. Acquia’s FAQ said sites still on 8.2 after October 1 would be upgraded to 8.4, and WP Engine says it upgrades at end of life. Others publish no date. Check your host’s own documentation.