Pick the closest one. I'll show you what's likely going on and what I'd do about it.
That warning is accurate, and it only gets worse with time.
Every PHP version has a fixed support window. After it closes, newly found security holes are not patched for that version, and hosts eventually force an upgrade or retire the version, sometimes with little notice. As of late 2026, PHP 8.1 and older are out of security support, and 8.2 reaches the end of its security window on 31 December 2026.
What I'd do: audit the site against a modern PHP version, fix or replace what breaks on a staging copy, then switch the live site over in a planned window.
Best fit: One-time PHP fix
You're right to be careful. The fix is to never test on the live site.
Sites break on upgrade because of abandoned plugins, themes with old code, or custom snippets that use removed PHP features. Those are findable in advance. I clone the site, upgrade the clone, and fix every error there. Live is only touched once the copy works, and I take a full backup first so it can be put back.
What I'd do: staging clone, compatibility scan, repair or replace the problem plugins, side-by-side check, then go live with rollback ready.
Best fit: One-time PHP fix
Unpatched software is something auditors and clients ask about.
Frameworks such as PCI DSS v4.0 expect known security vulnerabilities to be addressed promptly and software to be tracked, and privacy laws like GDPR expect "appropriate" security measures. Running end-of-life PHP with outdated plugins is hard to defend in that conversation. A one-off upgrade helps, but the gap reopens as soon as the next update is missed.
What I'd do: upgrade now, then keep PHP, WordPress core, plugins and themes patched on a schedule, with monthly reports you can hand to an auditor or client.
Best fit: Fix & Maintain
I'm a web engineer, not your auditor or lawyer. This work supports compliance; it doesn't certify it.
An unowned site is a liability that keeps aging.
When nobody is responsible, updates stop, backups go unchecked and the hosting login is a mystery. Then something fails on a busy day. The cheapest time to take ownership is before the emergency.
What I'd do: inventory what's there, verify backups, upgrade PHP and everything that depends on it, document the setup, and stay on as the person who keeps it healthy.
Best fit: Fix & Maintain
Those symptoms often trace back to the PHP and plugin layer.
"Deprecated" warnings, intermittent white screens and plugins that quit working are classic signs of code that no longer matches the PHP version running it. Newer PHP versions are also generally faster than older ones, so upgrading and cleaning up tends to help speed as well.
What I'd do: read the error logs, find the offending code, repair or replace it, upgrade PHP, and confirm the warnings are gone.
Best fit: One-time PHP fix