Everything Looks Fine, and That Is the Problem
Your WordPress site loads quickly. Plugins are current, the theme is up to date, and the dashboard shows no warnings worth worrying about. You may have run every update in the last month. Underneath all of that, the PHP version your site runs on may have reached its end of life months ago. When PHP reaches end of life, nobody sends you a notice, nothing in wp-admin turns red, and your host may never mention it.
This is one of the most common gaps we find on otherwise well-maintained WordPress sites. The owner has done everything the dashboard asks. The server layer, meaning PHP and the MySQL or MariaDB database, has quietly stopped receiving security fixes. The site keeps working exactly as before, and that is the trap. An unpatched runtime does not slow down, throw errors, or break pages. It just stops being defended.
Here is why that matters. When a security flaw is discovered in a supported PHP release, the PHP project ships a fix and hosts roll it out. When the same flaw exists in a version past its end of life, no fix is coming. The details of the vulnerability are often public, and the version you are running will stay exposed for as long as you run it.
The same applies to your database server. MySQL 5.7, for example, reached end of life in October 2023, yet it still runs underneath plenty of live WordPress sites, because nothing forces an upgrade and nothing on the WordPress side warns about it.
This article covers:
- What end of life actually means for PHP and MySQL
- Why the checks you already rely on miss it
- How to find and grade your own versions in a few minutes
- How to upgrade without breaking your site
- How to stay ahead of the next deadline
None of this requires developer skills. It does require looking somewhere the dashboard does not point you.
What PHP End of Life Actually Means
Every PHP release follows a published lifecycle with three stages. Knowing which stage your version is in tells you more about your risk than any plugin scan.
- Active support. The version receives bug fixes and security fixes. This is where you want to be.
- Security-only support. Ordinary bugs are no longer fixed, but security holes still get patched. You are still protected, but the end of support is approaching and you should plan your upgrade.
- End of life. No fixes of any kind. Any vulnerability found from this point on stays open permanently in that version.
Some real dates make this concrete. PHP 7.4 reached end of life in November 2022. PHP 8.0 followed in November 2023. PHP 8.1 security support runs to the end of 2025. If your site runs on any of those first two versions, it has gone without upstream security patches for a long time, no matter how current your plugins are.
Databases follow the same pattern. MySQL 5.7 is past end of life. MySQL 8.0 has a published end date in 2026. MariaDB versions each have their own maintenance window, and some short-term releases expire within a year or two.
A version that is past end of life is not the same as a version that is broken. That distinction catches people out. Your site will run on PHP 7.4 today just as it did in 2021. Plugin developers may still support it. WordPress itself still installs on it. Running and protected are two different states, and nothing about how your site behaves tells you which one you are in.
There is one nuance worth knowing. Some hosts run enterprise Linux distributions or commercial extended-support builds that backport security fixes into older PHP versions after the official end of life. If your host does this, an old version number does not automatically mean unpatched. But you have to ask, and you need a clear yes in writing. Most budget and mid-range shared hosts do not offer backports. They simply keep the old version available because removing it would break customer sites and generate support tickets.
Why Your WordPress Dashboard Doesn't Warn You
Most site owners assume that if something serious were wrong, WordPress would say so. Site Health exists for exactly this kind of problem, so a clean report feels like a guarantee. It is not, and the reasons are worth understanding.
Site Health judges PHP by WordPress’s own thresholds, not the PHP project’s calendar. WordPress flags PHP versions that fall below its recommended level, but that line is drawn around compatibility and the minimum WordPress is willing to support. It does not track the exact day a version stops getting security fixes. A version can be past its end of life and still not trigger a warning, especially in the period right after support ends.
The database gets even less attention. Site Health checks that your MySQL or MariaDB version meets the minimum WordPress needs to run. It does not tell you whether that version is still receiving security patches. A site on MySQL 5.7 can show a perfectly healthy database report.
The update screen only covers WordPress. Dashboard updates handle core, plugins, themes and translations. PHP and the database live on the server, outside WordPress’s control, so they never appear in that list. A screen that says everything is up to date is only talking about the parts WordPress manages.
Hosts have little reason to raise it. Forcing a PHP upgrade can break older plugins, and broken sites mean support tickets. Many hosts leave old versions in place, sometimes as the default for accounts created years ago. Some send a single email that ends up in a folder nobody checks.
Put those together and you get the situation we see repeatedly: a site owner who updates diligently, has no dashboard warnings, and is running a runtime that stopped receiving patches long ago. The obvious checks miss it because none of them were built to ask the question. The only reliable approach is to look up your exact versions and compare them against the published support dates yourself.
How to Check and Grade Your PHP and MySQL Versions
Finding out where you stand takes about five minutes. You need two version numbers and two reference pages.
- Find your PHP version. In wp-admin, go to Tools > Site Health, open the Info tab, and expand the Server section. Note the PHP version, including the minor number, for example 8.1 rather than just 8.
- Find your database version. On the same Info tab, expand Database. Note the server version and whether it says MySQL or MariaDB. MariaDB sometimes reports a long string, so look for the number after the word MariaDB.
- Check PHP against the official calendar. The supported versions page on php.net lists every current branch with its active support and security support end dates. Anything not listed there is past end of life.
- Check the database against its vendor’s lifecycle. Oracle publishes MySQL support dates, and the MariaDB Foundation publishes maintenance windows for each MariaDB release.
Then grade each component using a simple three-level scale:
- Green: actively supported. Receiving bug and security fixes. No action needed beyond noting the end date.
- Amber: security-only, or within six months of end of life. Still patched, but schedule your upgrade now rather than when the deadline arrives.
- Red: past end of life. Unpatched unless your host has confirmed in writing that it backports security fixes. Treat this as a priority.
Grade PHP and the database separately. It is common to find PHP in good shape while the database sits on a version that expired years ago, because PHP versions are easy to switch in a control panel and database upgrades usually require the host to act.
If either component comes back red, contact your host with a specific question: is this version receiving backported security fixes, and if not, when can I move to a supported version? A vague answer such as we keep our servers secure should count as a no.
Upgrading Without Breaking Your Site
The reason so many sites stay on expired versions is fear of breakage, and the fear is reasonable. Moving from PHP 7.4 to PHP 8.x removes and changes functions that older plugins and themes depended on. A careful process removes most of that risk.
- Take a full backup. Files and database, stored somewhere other than the server itself. Confirm you know how to restore it before you change anything.
- Update everything first. Bring WordPress core, every plugin and your theme to their latest versions. Many PHP 8 compatibility fixes are already in releases you have not installed yet.
- Remove what you don’t use. Deactivated plugins still sit on the server, and abandoned ones are the most likely to break on newer PHP. Delete anything inactive, and look for replacements for plugins that have not been updated in over a year.
- Test on staging. Most hosts offer a one-click staging copy. Switch the staging site to the target PHP version and click through the pages that matter: home page, contact forms, checkout, login and any custom features.
- Watch for errors. Turn on WordPress debug logging on staging and look for fatal errors and deprecation notices. A fatal error names the plugin or theme file responsible, which tells you exactly what to update or replace.
- Switch production during a quiet period. Most control panels change PHP versions in seconds. Check the live site immediately afterward, and keep the old version selected in your notes so you can roll back quickly if something you missed breaks.
Jump to the newest version your plugins support rather than the next one up. Moving from 7.4 to 8.0 only buys you a version that is also expired. Aim for a branch with at least a year or two of support remaining.
Database upgrades usually work differently. On shared and managed hosting you generally cannot change MySQL or MariaDB yourself. The host either migrates your account to a newer server or upgrades the server in place. Ask for a scheduled window, take a fresh backup beforehand, and test the site carefully once it is done.
Staying Ahead of the Next Deadline
Upgrading once fixes today’s problem. The underlying issue remains: support windows keep closing, and nothing in WordPress will tell you when the next one does. A supported version today becomes security-only in a year or two, and then reaches end of life. Each branch gets only a few years of support in total, so every site will face this again.
A few habits keep you out of the red:
- Record the end dates. When you confirm your PHP and database versions, write down their security support end dates and put a reminder in your calendar six months before each one. Six months gives you time to test without rushing.
- Re-check after host changes. Migrations, plan changes and server moves can reset your PHP version to the host’s default, which is not always current. Check the Site Health Info tab after any change on the hosting side.
- Re-check when you add plugins. A new plugin that only supports older PHP can quietly lock you into an expiring version. Check a plugin’s stated PHP requirements before installing it.
- Get backport promises in writing. If your host claims to patch older versions, keep that confirmation on file and ask again each year. Policies change.
- Treat amber as action. The security-only stage is a planning window, not a resting place. Starting the upgrade at amber means you never spend a day unpatched.
The real lesson of PHP and MySQL end of life is about visibility. The WordPress dashboard is very good at showing what WordPress controls and completely silent about the server underneath it. A site can be fully updated, report healthy, and still run on software that stopped receiving security fixes long ago. Grading your server stack against published lifecycle dates, rather than trusting the absence of warnings, is the only way to know you are protected.
Check your two version numbers today. If both are green, put the end dates in your calendar. If either one is red, you now know exactly what to ask your host.
Does Your Site Have This Problem?
Every check in this article runs automatically on the sites we look after. You can run the same health checks on your own site in seconds with the free SiteHale plugin — no account, nothing transmitted anywhere. Or have us do it: we’ll crawl your site and send you a written report, free.