Security

WordPress PHP End of Life: How to Check and Upgrade Safely

Which PHP versions are still supported, how to see what your site runs, and how to upgrade without a white screen.

Quick Answer: PHP 8.2 security support ends on 31 December 2026, 8.3 on 31 December 2027, 8.4 on 31 December 2028 and 8.5 on 31 December 2029. Find your version under Tools, Site Health, Info, Server in WordPress. Upgrade on a staging copy after updating or replacing old plugins, then switch production with a rollback plan.

Want Us to Check Your PHP Version?

Tell us about your site and we'll get back to you within one business day.

Your host emails a notice, or Site Health in WordPress shows a warning that your PHP version is out of date. PHP is the language WordPress runs on, and each version has an end date after which it stops getting security fixes. Here is how to find out where your site stands and how to upgrade without taking it down.

Where PHP versions stand now

The PHP project publishes its supported versions. As of this writing, the dates for security support are:

PHP versionSecurity support ends
8.231 December 2026
8.331 December 2027
8.431 December 2028
8.531 December 2029

Versions older than 8.2 no longer appear in PHP's list of supported versions. WordPress.org suggests that your host run PHP 8.3 or newer.

If your site is on PHP 8.2, you have until the end of the year before it stops getting security fixes. If it is on anything older, it is already past that point.

Why it matters for a business site

An unsupported PHP version means that any flaw found in PHP itself goes unpatched. It also tends to be the first thing that comes up in a security review. A cyber insurance form or a client questionnaire often asks whether you run end-of-life software, as we explain in cyber insurance and WordPress.

How to check your version

In your WordPress dashboard, go to Tools, then Site Health, then the Info tab, and open the Server section. The PHP version is listed there. Your host's control panel also shows it and usually lets you change it.

Why upgrades break sites

PHP upgrades rarely break WordPress core. They break old plugins, themes and custom code that rely on features that have been deprecated or removed. A site that has not been maintained for a while can have several of these, which is why a quick version switch can end in a white screen. Our guides to the white screen of death and the critical error message cover what that looks like.

A safer upgrade path

  • Take a full backup and store it off the server.
  • Test on a staging copy. Set the new PHP version there, not on the live site.
  • Update plugins and themes first. Replace anything that is abandoned or has not been updated in a long time. See what to do with an abandoned plugin.
  • Click through what matters: checkout, forms, logins and any custom features. Check the error log for warnings.
  • Switch production at a quiet time, with the ability to roll back to the previous PHP version if something fails.
  • Watch the site for the next few days.

If you would rather someone else handled it

Upgrading PHP safely means a staging copy, testing and a rollback plan. That is the same discipline as WordPress change management. Our maintenance plan includes tested updates, and a free site audit will tell you what your site is running and what needs to change first.

Related Guides

Martin Van Den Boogerd
Martin Van Den Boogerd
Founder & Owner, CriticalWP, a WebOps agency for WordPress — background in cybersecurity and municipal government infrastructure
More about Martin →

Common Questions

PHP's published schedule lists security support for 8.2 until 31 December 2026.
WordPress.org suggests that your host run PHP 8.3 or newer. Check what your plugins and theme support before you upgrade.
In the dashboard, go to Tools, then Site Health, then the Info tab, and open the Server section. Your host's control panel also shows it.
Yes, usually because of old plugins, themes or custom code that rely on features that were deprecated or removed. Test on a staging copy first.
PHP stops receiving security fixes, so any newly found flaw in PHP itself goes unpatched. It can also come up in cyber insurance forms and client security reviews.

Find out what your site is running.

A free site audit checks your PHP version, updates, plugins and backups, and tells you what to fix first.