07904 288451 Let’s talk

PHP 8.2 end of life and October’s security update: what to do

Two critical PHP flaws were patched on 21 October, and PHP 8.2 stops getting security fixes on 31 December. Here is what that means for a WordPress site, and what to ask whoever hosts yours.

Business 4 min read By Martin Phillips

In short

PHP released fixes for two critical vulnerabilities on 21 October 2026, and PHP 8.2 stops receiving security fixes on 31 December 2026. If your WordPress site runs on PHP, check that your host has installed 8.2.35, 8.3.36, 8.4.27, 8.5.12 or later, then plan a tested move to PHP 8.3 or 8.4 before the end of the year. Updating WordPress or your plugins does not fix either issue.

Lines of colourful code on a dark screen, illustrating the PHP language that WordPress runs on

What happened to PHP in October 2026?

On 21 October 2026 the PHP project shipped an urgent security release fixing two vulnerabilities, each rated 9.2 out of 10. Under particular server configurations they can let an attacker run code on the web server without logging in. The flaws sit in PHP itself, the language WordPress runs on, rather than in WordPress, your theme or your plugins (Help Net Security).

The fixed versions are:

  • PHP 8.2.35
  • PHP 8.3.36
  • PHP 8.4.27
  • PHP 8.5.12

Is PHP 8.1 or older covered?

Not by a normal release. PHP 8.1 and earlier are already out of support, so there is no standard update for them. Some hosts and Linux distributions ship their own patched builds of older versions, but the safe assumption is that a site on 8.1 or older needs moving to a supported version (summary of fixed versions).

Why doesn’t updating WordPress fix it?

Because the vulnerable code runs on the server, underneath WordPress. Updating WordPress, your theme or your plugins changes nothing about the PHP version the server uses. A security plugin, firewall or CDN can block plenty of other attacks, but it is not a substitute for the patched version: the host has to install it and restart the services that run PHP.

It is also worth checking the version that actually serves your website, which is not always the same one a command line or control panel reports first.

Rack of web servers in a data centre, where PHP runs underneath a WordPress site
Photo: Kevin Ache on Unsplash

What does PHP 8.2 end of life mean for my website?

PHP 8.2 receives its last security fixes on 31 December 2026. From 1 January 2027 the PHP project stops publishing fixes for it, so any flaw found afterwards may never be patched upstream. Your site will keep working, but it will be running on software nobody is maintaining (Xictron, citing php.net).

This affects a lot of sites. In September 2026 around 62% of WordPress installations reporting to WordPress.org ran PHP 8.2 or older, and WordPress recommends PHP 8.3 or newer.

  • PHP 8.1: security support ended 31 December 2025
  • PHP 8.2: security support ends 31 December 2026
  • PHP 8.3: security support until 31 December 2027
  • PHP 8.4: security support until 31 December 2028
  • PHP 8.5: security support until 31 December 2029

How do I check which PHP version my site uses?

Any of these will tell you:

  • In WordPress, go to Tools, then Site Health, then the Info tab, and open the Server section
  • In your hosting control panel, look for the PHP version or PHP selector setting
  • Ask your host or developer directly, in writing, which version serves your site and whether the October update is installed

How do you upgrade PHP without breaking the site?

Most sites move from 8.2 to 8.3 or 8.4 without drama, but an old theme or an abandoned plugin can fail on a newer version. The safe sequence is:

  • Take a full backup, files and database, and check it can be restored
  • Update WordPress, the theme and plugins first, on the current PHP version
  • Switch a staging copy of the site to PHP 8.3 or 8.4
  • Test what matters: forms, logins, checkout and payments, bookings, search
  • Check the PHP error log for warnings, not just visible errors
  • Switch the live site at a quiet time and keep a way back to the old version for a few weeks
Hands typing on a laptop while testing a website before a PHP upgrade
Photo: Ben Kolde on Unsplash

What if an old plugin or theme won’t run on newer PHP?

Then it was already a risk. Plugins that have not been updated for years are a common way into WordPress sites, PHP version aside. The fix is usually to replace the plugin with a maintained alternative or have a developer correct the code. Occasionally the honest answer is that the site has been held together for too long and a rebuild costs less than continuing to patch it.

What has Rockhopper done for its clients?

We checked the sites we host and contacted clients on the evening the vulnerabilities were announced. Keeping PHP current is part of our website care plans, and we don’t charge hosting clients for PHP version support.

If someone else looks after your site, these three questions are worth sending them today:

  • Which PHP version serves my website right now?
  • Has the 21 October 2026 PHP security update been installed?
  • When will my site move off PHP 8.2, and how will it be tested first?

A quick checklist before 31 December

  • Confirm the October 2026 PHP update is installed on your server
  • Find out which PHP version your site runs
  • If it is 8.2 or older, book a tested move to 8.3 or 8.4
  • Replace any plugin that has not been updated in the last year
  • Make sure backups exist, are offsite and have been test-restored

Need a hand with your site?

Not sure where your site stands? Get in touch and we will take a look, or read how our care plans keep WordPress sites updated, backed up and secure.

Questions

Related
questions.

Short answers to the things people ask next.

Ask us yours
Is my WordPress site affected by the October 2026 PHP vulnerabilities?

If the server runs a PHP version older than 8.2.35, 8.3.36, 8.4.27 or 8.5.12, it should be updated. Whether a particular site can actually be exploited depends on how the server is set up, but the fix is the same either way: install the patched PHP version.

Will my website stop working when PHP 8.2 reaches end of life?

No. The site keeps running after 31 December 2026, but PHP 8.2 stops receiving security fixes, so any new flaw may stay unpatched. Moving to PHP 8.3 or 8.4 avoids that.

Which PHP version should a WordPress site use?

PHP 8.3 or 8.4 for most sites, tested on a staging copy first. WordPress recommends 8.3 or newer, and both versions receive security fixes for at least another year.

Does a WordPress security plugin protect against this?

Not fully. Security plugins and firewalls block many attacks, but these flaws are in PHP on the server. Only installing the patched PHP version fixes them.

Do you charge for PHP upgrades?

We don’t charge hosting clients for PHP version support, and keeping PHP current is part of our care plans, which start from £45 a month. For sites we don’t host, we look at the site first and quote for any compatibility work.

Start a conversation

Something in mind?
Let’s talk.

Tell us what you are trying to achieve and we will tell you honestly what it takes, what it costs and whether we are the right people for it.

We reply within one working day. Your details are used to answer your enquiry and nothing else.

WhatsApp