Key Takeaways
- PHP 8.2 reaches end of life on December 31, 2026. After that date, no more security fixes.
- 23% of WordPress sites run on PHP 8.2. Together with older versions, more than half of all WordPress sites will run on unsupported PHP from January 1.
- Your site won’t stop working on January 1, but the next serious PHP vulnerability won’t be fixed for it.
- Upgrade to PHP 8.3 at minimum. PHP 8.4 gives you two more years of support if your plugins are ready.
- Always test on a staging copy first. Most upgrade problems come from outdated plugins, not WordPress itself.
PHP 8.2 stops receiving security fixes on December 31, 2026. If your WordPress site still runs on it, plan an upgrade to PHP 8.3 or newer now, as WordPress itself recommends. Test the switch on a staging copy first, then update the live site before the deadline.
We maintain WordPress sites for clients in the US, UK, and Europe, and PHP upgrades are a regular part of that work. Here’s what’s changing, who’s affected, and how to upgrade safely.
What end of life means for PHP 8.2
Every PHP version gets two years of active support, with bug and security fixes, and then two years of security fixes only. PHP 8.2 left active support at the end of 2024. Its security support ends on December 31, 2026 (php.net).
Nothing breaks on January 1. Your site will keep loading exactly as before. What changes is that when the next PHP vulnerability is found, PHP 8.2 won’t get a patch. Your site stays exposed until you move to a supported version.
How many WordPress sites are affected
A lot. According to WordPress.org Stats, 23% of WordPress sites run on PHP 8.2. Another 31% already run on PHP 8.1 or older, versions that lost security support earlier. As of January 1, that’s more than half of all WordPress sites (54%) on a PHP version that no longer gets security fixes.
Security fixes end December 31, 2026 23.0%
Already without security fixes 30.9%
Still supported 46.1%
Hosting companies are already moving. WP Cloud, the platform behind WordPress.com, removes PHP 8.2 on December 15, 2026, two weeks before the official end of life. Expect other hosts to announce their own dates.
Why staying on PHP 8.2 is a risk
In October 2026, the PHP project released urgent fixes for two critical vulnerabilities known as PHP2Shell. They let attackers run code on a server without logging in. PHP 8.2 still got a fix then, in version 8.2.35. We covered what that meant for WordPress sites in our PHP2Shell post.
If the same kind of flaw is found after December 31, PHP 8.2 won’t get that fix. Updating WordPress or your plugins won’t help either, because the problem sits in PHP itself, on the server. The only fix is moving to a supported PHP version.
How to check which PHP version your site runs
In WordPress, go to Tools › Site Health › Info and open the Server section. The PHP version is listed there. You’ll also find it in your hosting control panel, usually under PHP settings or software.
If you see 8.2 or anything older, read on.
Which version should you upgrade to: PHP 8.3, 8.4, or 8.5?
WordPress recommends PHP 8.3 or greater. Here’s how long each supported version will get fixes:
| PHP version | Active support until | Security fixes until |
|---|---|---|
| PHP 8.3 | December 31, 2025 | December 31, 2027 |
| PHP 8.4 | December 31, 2026 | December 31, 2028 |
| PHP 8.5 | December 31, 2027 | December 31, 2029 |
Our recommendation: PHP 8.3 at minimum, so you’re safe through 2027. If your plugins and theme already support PHP 8.4, go straight to 8.4, and you won’t need to think about this again until the end of 2028. PHP 8.5 is the newest version, and some plugins still need time to catch up.
How to upgrade without breaking your site
WordPress core runs fine on PHP 8.3 and newer. When an upgrade breaks something, it’s almost always an outdated plugin or a custom theme. That’s why the order of steps matters:
If something breaks on staging, you’ve lost nothing. Update or replace the plugin that causes the error, test again, and only then touch the live site. If your host doesn’t offer staging, a developer can set up a copy for you.
Who should handle the upgrade?
On managed WordPress hosting, the host usually changes the PHP version for you, or tells you when they will. Ask them for the date, so you can test before it happens. On a self-managed server or basic shared hosting, it’s on you or your developer.
Either way, someone needs to check the plugins and test the site, and that’s the part that takes time. If you’d rather hand it off, our WordPress maintenance plans start at $200 a month, include development hours for changes like this, and every plan begins with a free site review.
FAQ
When does PHP 8.2 reach end of life?
On December 31, 2026. After that date, PHP 8.2 will no longer receive security fixes.
Will my site stop working on January 1?
No. Your site keeps running as before. It just won’t get a fix if a new PHP vulnerability is found.
Until when is PHP 8.3 supported?
PHP 8.3 gets security fixes until December 31, 2027. PHP 8.4 is supported until the end of 2028.
Will updating PHP break my plugins?
WordPress core runs fine on PHP 8.3 and newer, but outdated plugins or custom themes can throw errors. That’s why you test on a staging copy first.
Does my host update PHP automatically?
Some managed hosts do, usually with advance notice. Many shared hosts leave it to you. Check your hosting dashboard or ask your host for their date.