What "outdated PHP version detected" means

You log in to your website’s dashboard and there’s a red or orange box at the top: your site is running on an outdated version of PHP. Maybe it came from WordPress, from a security plugin, or from your hosting company in an email. The site still works, so it’s tempting to close the box and carry on.

That’s understandable, and it’s also how a small job turns into an emergency later.

What the warning means

PHP is the software that runs behind most websites, including every WordPress site and a lot of online shops and custom-built portals. A new version comes out every year, and each version gets security fixes for a few years before it’s retired.

The warning means your site runs on a version that has been retired or soon will be. It still works today. What’s changed is that when someone finds a security hole in that version, nobody will fix it.

How urgent is it

It depends on which version you’re on. You can usually see it in the warning itself, or under Tools, then Site Health, then Info in WordPress.

• 8.3 or newer: you’re fine. WordPress itself recommends 8.3 or newer.
• 8.2: fine for now, but its security fixes end on 31 December 2026. Plan the upgrade in the next few months.
• 8.1 or older: already without security fixes. Your site is exposed to any problem found from now on, and your hosting company is likely to move you onto a newer version soon whether you’re ready or not.

Why people put it off

Mostly because they’ve heard that updating PHP can break a site, and that’s true. Older plugins, themes and custom code sometimes rely on things newer versions no longer allow. When that happens you might see a blank page, an error, or a contact form that quietly stops sending.

The risk is real, but it’s manageable, and it only grows the longer you wait, because each skipped version adds more changes to deal with at once.

How to upgrade without breaking the site

1. Make a copy of the site. Most hosts offer a staging copy with one click. Never try the upgrade on the live site first.
2. Update everything else first. WordPress, the theme and every plugin. Remove plugins you no longer use.
3. Switch the copy to the newer PHP version and click through the parts that matter: the homepage, the shop or booking form, logging in, any emails the site sends.
4. Fix what breaks on the copy, then repeat the switch on the live site at a quiet time.
5. Keep a way back. Know how to switch the live site to the old version for a day if something was missed.

On a well-kept site this takes an afternoon. On a site that was custom-built years ago, or that nobody has touched in a long time, it’s a small project, and worth handing to someone who has done it before. If your hosting company has already moved you and the site broke, start with what to do when a hosting update breaks your website.

If you've seen this warning and don't have anyone to ask, reach out to us. We'll tell you which version you're on, what it would take to upgrade, and do it on a copy first so your customers never see a broken site.