If your site still runs PHP 7.4, 8.0 or 8.1, it no longer gets security fixes, including the fix for the October 2026 PHP2Shell flaws. PHP 8.2 joins that list on 31 December 2026.
I upgrade it for you: backup first, staging copy, test everything that matters, fix what breaks, then switch the live site. Free version check, fixed quote before any work.
Web developer · Hundreds of sites worked on · WordPress · WooCommerce · Joomla · Many hosting platforms
I reply personally within one working day with a plain answer: your PHP version, whether you need to upgrade, and a fixed quote if you do.
No passwords needed for the check. Never send login details by email.
Urgent? +27 66 212 7955 (call or WhatsApp) · rob@chiefgrowthengineer.com
| Your PHP version | Security fixes until | What to do |
|---|---|---|
| 8.5 | 31 Dec 2029 | Stay. Keep on the latest patch release (8.5.12 or newer). |
| 8.4 | 31 Dec 2028 | Stay. Keep on the latest patch release (8.4.27 or newer). |
| 8.3 | 31 Dec 2027 | Stay for now. Keep on the latest patch release (8.3.36 or newer). |
| 8.2 | 31 Dec 2026 | Patch to 8.2.35 now, and upgrade to 8.3 or 8.4 before the end of the year. |
| 8.1, 8.0, 7.4 | Already ended | Upgrade. No official security releases, including for PHP2Shell. |
| 7.3 and older | Long ended | Upgrade, and expect compatibility work. |
Not sure which version you're on? In WordPress it's under Tools, Site Health, Info, Server. In cPanel, look for MultiPHP Manager. The full guide is here: how to check your website's PHP version, and here's how to change it on each host. Or send me your address and I'll check it for you.
I'm Rob Louw, a web developer and engineer. I've worked on hundreds of websites across many hosting platforms and content management systems, including WordPress, WooCommerce and Joomla, for clients in South Africa, the UK, Ireland, the Middle East and the US. PHP upgrades, patching and keeping sites secure are part of that everyday work, and I do it myself. There's no call centre and no junior team. More about me.
Why a web developer, not a security firm? A security scan tells you what is wrong. A developer fixes it, then makes sure your site, forms and checkout still work afterwards. You get both from one person who knows how these sites are built and hosted.
Prefer to talk first? WhatsApp or email me and I'll reply within one working day: rob@chiefgrowthengineer.com or +27 66 212 7955.
For most sites, 8.3 or 8.4. Both have support left and wide plugin support. I'd only go to 8.5 if your theme and key plugins list it. I don't recommend 8.2 as a destination, because you'd be doing this again in a few weeks.
On a big jump it can, which is why the live site isn't touched until a staging copy has been upgraded and tested. If something old can't be made to work, I'll tell you before the switch and suggest a replacement.
You can, and on a simple site with current plugins it often works. The risk is a checkout, form or page builder that fails quietly afterwards. If you do it yourself, take a backup first and test the pages that make you money straight after.
That notice means your server runs an older PHP version than WordPress recommends. The upgrade happens in your hosting panel or on the server, not inside WordPress. It's exactly the job this service covers.
It depends on how far your site has to move and how many plugins need work. The version check is free, and you get a fixed quote before anything starts.
Yes. Sites on PHP 8.1 or older can't get the official PHP2Shell fix, so upgrading is how they get protected. More on that here: PHP2Shell website check.
Upgrade once, to a version with years of support left. Start with a free check.
Check my PHPOr email rob@chiefgrowthengineer.com · call or WhatsApp +27 66 212 7955