
Why outdated PHP puts your WordPress website at risk
PHP is the language WordPress runs on. When your server uses a version that is no longer supported, known security holes stay open for good, and no plugin or firewall can fully make up for it. Here is what that means, how to check your version, and how to upgrade without breaking your site.
- Every PHP version gets security fixes for a limited time, then none at all.
- An unsupported version leaves every flaw found after that date open on your server.
- Newer PHP versions are usually faster too.
- Upgrade on a staging copy first, fix conflicts, then switch the live site.
- Make PHP upgrades part of regular maintenance, not a one-off panic.
What PHP is, and why the version matters
Your WordPress website is a collection of PHP files. Every time someone opens a page, the server runs those files to build it: reading your theme, asking the database for content, and running each active plugin. WooCommerce shops, booking systems and contact forms all depend on PHP.
Like any software, PHP gets new versions. The PHP project supports each version for a limited time: a period of active support with bug and security fixes, followed by a period of security fixes only. After that, the version reaches end of life, and the PHP team stops fixing it entirely.
What goes wrong on an old version
- Security holes stay open. When researchers find a vulnerability in PHP itself, supported versions get a patch. End-of-life versions do not. Details of fixed vulnerabilities become public, so attackers know exactly what to look for.
- Plugins stop supporting you. Plugin and theme developers drop old PHP versions over time. You end up stuck on outdated plugin versions, which have their own unpatched holes.
- Performance suffers. Newer PHP versions typically run the same code noticeably faster, which helps speed and Core Web Vitals.
- WordPress warns you. The Site Health screen flags outdated PHP, and future WordPress versions raise their minimum requirements.
- Hosts eventually force the change. Many hosts remove old versions without much notice, and an untested forced upgrade can take your site down.
How to check your PHP version
- In WordPress, go to Tools and then Site Health, open the Info tab and expand Server. The PHP version is listed there.
- Or check your hosting control panel, which usually shows the PHP version per domain.
- Compare it with the supported versions listed on the official PHP website. If yours is not on the supported list, it is time to upgrade.
How to upgrade safely
- Take a full backup of files and database, stored away from the server.
- Create a staging copy of the site, an exact private duplicate.
- Update WordPress, the theme and all plugins on staging first. Many PHP problems disappear once everything is current.
- Switch staging to the new PHP version.
- Test thoroughly: every page template, forms, search, login, cart and checkout, bookings and anything custom. Check the error log.
- Fix or replace what breaks. Abandoned plugins with no update for a long time are the usual culprits and should be replaced.
- Switch the live site at a quiet time, then test again.
- Keep the backup until you are confident everything works.
What usually breaks, and why
| Symptom after upgrading | Likely cause |
|---|---|
| White screen or critical error | An old plugin or theme using removed PHP functions |
| Contact form stops sending | Outdated form or mail plugin |
| Layout broken on some pages | Old page builder or theme version |
| Warnings shown on the page | Deprecated code; update or hide warnings on live sites |
| Checkout errors | Outdated payment gateway extension |
Common mistakes
- Upgrading the live site directly without testing.
- Upgrading PHP before updating plugins and theme.
- Ignoring abandoned plugins because "they still work".
- Waiting for the host to force it, usually at the worst moment.
- Showing PHP errors publicly, which can reveal information about your server.
How often to think about PHP
Check your PHP version at least twice a year, and plan an upgrade well before your version reaches end of support. With a maintained site, each upgrade is a small, routine job. Left for years, it becomes a rebuild.
Questions people ask
Will upgrading PHP change how my site looks?
Not if everything is compatible. PHP runs behind the scenes. Visual problems only appear when a theme or plugin is too old for the new version.
Can I just stay on the old version if nothing breaks?
The site may keep working, but every new PHP vulnerability discovered after end of life stays open, and your plugins gradually stop receiving updates. Working is not the same as safe.
Does this apply to non-WordPress sites?
Yes. Any website or application built on PHP, including Laravel, Joomla, Drupal, Magento or custom code, has the same issue.
A real-world example of how it goes wrong
A typical pattern: a business website was built several years ago and has run quietly since. Nobody updated PHP because "it works". Over time, plugin developers stopped supporting that PHP version, so plugins could not be updated either. A vulnerability in one of those outdated plugins became public, bots started scanning for it, and the site was quietly injected with spam links. The first sign was a warning in Google search results, weeks later. Cleaning up, restoring rankings and upgrading everything at once cost far more than steady maintenance would have.
Checklist before you upgrade
- Full offsite backup taken and restore tested.
- Staging copy available.
- List of plugins with their last update dates.
- Custom code identified, so a developer can check it.
- A quiet time agreed for the live switch.
- Someone available to test forms, checkout and key pages afterwards.
How we handle it
Our website management plans include tested PHP upgrades on staging, plugin updates and compatibility fixes, so your site never sits on an unsupported version. On our managed hosting, current PHP versions are available and kept patched, and we plan upgrades with you. Every new client starts with a free audit that checks this first. For the wider picture, read 8 security mistakes that get business sites hacked.