PHP 8.2 stops getting security fixes on 31 December: what to check on your WordPress site
WordPress runs on PHP, the programming language your hosting server uses to build each page. Like any software, each PHP version is only supported for a set time. According to the official PHP supported versions page, PHP 8.2 gets its last security support on 31 December 2026. After that, newly found security problems in 8.2 won't be fixed.
That's about six weeks away, and it lands in the middle of the summer break, when a lot of small businesses would rather not be thinking about their website at all. So now is a good time to check.
Why it matters
A site on an unsupported PHP version usually keeps working. Nothing switches off on 1 January. The risk is quieter than that:
- Security fixes stop. The PHP project's end-of-life page says users of unsupported releases "may be exposed to unpatched security vulnerabilities".
- Plugins and themes move on. Developers test against current PHP versions, and over time some stop supporting older ones.
- Hosts eventually force the upgrade. Many hosting companies move customers off old PHP versions on their own schedule, and that's a worse time to find out a plugin doesn't cope.
WordPress itself currently recommends PHP 8.3 or greater, so 8.2 is already below the recommendation.
How to check which PHP version you're on
You don't need server access for this. In your WordPress dashboard, go to Tools → Site Health, open the Info tab and expand the Server section. The PHP version is listed there.
Most hosting control panels also show it, usually on a page called something like "PHP settings" or "PHP version manager".
If it says 8.3, 8.4 or 8.5, you're on a supported version for now. If it says 8.2 or lower, it's worth planning an upgrade.
Which version to move to
As of today, the PHP project lists security support ending on:
- PHP 8.3: 31 December 2027
- PHP 8.4: 31 December 2028
- PHP 8.5: 31 December 2029
A newer version buys you more time, but only if your plugins and theme are ready for it. For most small business sites I'd aim for the newest version your plugins clearly support, rather than the newest version available.
The order I'd do the upgrade in
Changing PHP is usually a single setting on the host. The work is making sure the site still behaves afterwards.
- Take a full backup and confirm it restores. Files and database, not just one or the other.
- Update WordPress core, plugins and theme first. Older plugin versions are the most common reason a site breaks on a newer PHP. Updating them on the version you're already on keeps the two changes separate.
- Look for plugins that are no longer maintained. If a plugin hasn't had an update in a couple of years, check whether it lists support for your target PHP version. This is often the moment to replace it.
- Test on a staging copy if your host offers one. Switch the staging site's PHP version and click through it before touching the live site.
- Switch the live site and check the important paths. Home page, contact form (and that the message arrives), login, and for a WooCommerce store, a full test order through checkout.
- Keep an eye on errors for a few days. Site Health, your host's error log, or a monitoring tool will show warnings that don't appear on screen.
If something does break, most hosts let you switch the PHP version back straight away, which is why it's worth doing this before the deadline rather than after.
Custom code needs a closer look
Sites with custom plugins or theme changes need more care. Code written years ago for PHP 7 can use functions that newer PHP versions have deprecated or removed. The PHP manual has migration guides for each version that list these changes, and going through custom code against them before switching is quicker than tracking down a white screen afterwards.
Where I fit in
Keeping PHP current is part of the WordPress and WooCommerce maintenance I do for small NZ businesses, along with updates, backups and checking the custom code I've built. If you're not sure what your site is running or whether it's ready to move, send me a short note with your site address and I'll take a look.