// WordPress guide

No more security fixes for PHP 8.2 from 31 December 2026. Here's what it means for your WordPress site.

Last updated

The short version

From 31 December 2026, PHP 8.2 gets no more security fixes. If your WordPress site runs on it, any flaw found after that date stays open for good. In October 2026 every version of PHP had to be patched in a hurry, so that's not a theoretical risk.

Your host has to upgrade the PHP version. Updating WordPress doesn't do it. Upgrading can break older plugins and themes, so test it before it goes live.

What PHP is, and why your site depends on it

WordPress is written in PHP. Every time someone opens a page, your server runs PHP to build it. WordPress, your theme and every plugin all sit on top of PHP. When PHP has a hole in it, so does everything built on it.

PHP versions get security fixes for a set period, then they stop. For 8.2, the cut-off is 31 December 2026.

What happened in October 2026

In October 2026, a pair of flaws in PHP were made public. They're known as PHP2Shell (CVE-2026-109618 and CVE-2026-109619). They let an attacker run commands on a web server without logging in. The bugs went back to PHP 5.4, released in 2012, so they'd sat unnoticed for around 14 years.

The NCSC said organisations using any version of PHP were affected. It advised taking sites offline if they couldn't be patched quickly, and some council, NHS and government sites did exactly that. Supported versions got a patch. Older versions had no patch at all, so those sites needed a full upgrade.

A developer we work with looks after hundreds of WordPress sites. Patching them all was a major job. The plugin-free sites we build don't run PHP, so there was nothing to patch.

What changes from 31 December 2026

Nothing visible. Your site keeps loading as normal, which is the problem. The next time a PHP flaw is found, 8.2 won't get a fix. The NCSC expects more PHP vulnerabilities to follow the October ones.

WordPress security releases have also picked up. In the six months to November 2026 there were 7 security releases fixing 47 vulnerabilities. In the six months before that, there were 2 releases fixing 10.

How to check which PHP version your site uses

  • In WordPress: go to Tools → Site Health → Info → Server. The PHP version is listed there.
  • In your hosting control panel: look for "PHP version", "Select PHP version" or "MultiPHP Manager".
  • Ask your host or developer. It's a one-line email: "Which PHP version is our site on, and when are you upgrading it?"

PHP 8.1 and older had already lost security support, and 8.2 loses it from 31 December 2026. If your site is on any of them, plan the upgrade now. On the oldest versions, the October 2026 flaws may still be open.

Want to see how your site performs while you're at it? Try our free website speed test.

Your options

  1. Upgrade PHP properly. Take a backup and copy the site to a staging area. Switch that copy to a supported PHP version and check every page, form and plugin works. Fix what breaks, then switch the live site over. Old or abandoned plugins are usually what breaks.
  2. Have someone do it for you. If you'd rather not touch it, we'll do the upgrade and testing.
  3. Take PHP out of the picture. Most small business sites don't need WordPress at all. A plugin-free site has no PHP, no database and no login page, so deadlines like this one don't apply to it.

For the wider picture of how WordPress sites get hacked, read our WordPress security guide.

Questions

Will my site stop working after 31 December 2026?

No. It keeps working. It just gets no more security fixes, so any new flaw stays open.

I updated WordPress and my plugins. Am I covered?

No. Those updates don't change PHP. Your host controls the PHP version.

My host says they handle it. Do I need to do anything?

Ask them two things: which version you're on now, and when they're moving you. Then check your site works afterwards. Hosts upgrade PHP, but they don't test your plugins.

Was my site affected by PHP2Shell in October 2026?

If it runs on PHP, which every WordPress site does, it was exposed until your host patched it. If you're not sure it was patched, ask your host.

Every job starts with a call

Your move.

Fifteen minutes on the phone. We’ll look at your site, tell you straight what we’d do, and you decide from there.

Rather ring? 01376 395118

Book your free call.

Fifteen minutes on the phone. We look at your site first, then tell you straight what we’d do. No pitch deck, no obligation.