Skip to main content

PHP 8.2 loses security support on 31 December 2026. That date has been public since 2022, so on paper nobody should be caught out. We pulled every archived copy of the WordPress.org PHP version statistics from the past year to see how the last deadline went. On 10 January 2026, ten days after PHP 8.1 reached end of life, 50.7% of WordPress sites were running a PHP branch with no security support. On current pace, the figure on 1 January 2027 will be about 48%. A full year of upgrades will have bought roughly three points.

TL;DR

  • PHP 8.2 reaches end of life on 31 December 2026. Today 31.5% of WordPress sites already run unsupported PHP and another 22.3% run 8.2, so 53.8% are unsupported from 1 January.
  • The last cliff looked the same: 50.7% of WordPress ran unsupported PHP on 10 January 2026, ten days after PHP 8.1 expired.
  • Sites are migrating at about 4.6 points a month, which puts the 1 January figure near 48%. The 8.2 cohort itself has shrunk by only five points in ten months.
  • From 1 January, only PHP 8.5 and 8.6 still receive bug fixes. That is 6.9% of WordPress.
  • Six weeks is enough for most sites to move to PHP 8.4 or 8.5, if the plugin audit starts now.

What actually happens on 31 December

PHP branches get two years of active support followed by two years of security-only fixes. PHP 8.2 was released on 8 December 2022, its active support ended on 31 December 2024, and its security support ends on 31 December 2026. After that, the PHP project ships nothing for it: no patch when the next remote code execution bug lands, however severe.

Two other branches change status on the same night, and they get less attention. PHP 8.4 leaves active support and becomes security-only until the end of 2028. PHP 8.3 has been security-only since last January and stays that way until 31 December 2027. So from 1 January, the only branches still receiving ordinary bug fixes are 8.5 and 8.6, the latter released two days ago on 19 November.

The WordPress.org stats API publishes the PHP version share across every site that checks in for updates. Today it reads like this:

  • 31.5% on PHP 8.1 or older, already unsupported (PHP 7.4 alone is 14.1%)
  • 22.3% on PHP 8.2, unsupported in 40 days
  • 39.3% on 8.3 or 8.4, security fixes only from 1 January
  • 6.9% on 8.5 or 8.6, fully supported

We have seen this film before

A single snapshot tells you very little. The Internet Archive has captured the same API endpoint several times this year, so we can watch the curve move. Each row below is the share of WordPress running PHP that is unsupported today (8.1 and older), plus the share on 8.2:

Snapshot 8.1 and older PHP 8.2 Unsupported from 1 Jan 2027
10 January 2026 50.7% 27.3% 78.0%
25 February 2026 48.1% 26.6% 74.8%
27 September 2026 37.6% 24.5% 62.2%
2 November 2026 32.9% 22.8% 55.8%
21 November 2026 (live) 31.5% 22.3% 53.8%

Read the second column first. Ten days into 2026, half of WordPress was running unsupported PHP. Over the following ten months that share fell steadily, from 50.7% to 31.5%. That is real progress, and it is about to be wiped out in a single night, because the 22.3% on PHP 8.2 joins the unsupported group at midnight on 31 December.

Between 27 September and today the combined figure fell by 8.4 points in 55 days, roughly 4.6 points a month. Forty days remain. Even if that pace holds through the Christmas change freeze, which it will not, the figure lands at about 48%. The industry will start 2027 almost exactly where it started 2026.

Why the 8.2 cohort barely moves

The interesting column is the third one. PHP 7.4 fell from 22.1% to 14.1% this year. PHP 8.2 fell from 27.3% to 22.3%, just five points in ten months, while its deadline was the nearest one on the calendar.

Our reading is that upgrades are driven by pain, not by dates. Sites on 7.4 hit visible problems: plugins that refuse to install, hosts that charge an extended-support fee, page builders that drop compatibility. Sites on 8.2 hit none of that. Everything works, the hosting dashboard shows a green tick, and the version number looks modern. Nothing tells the owner that the clock has run out until the first unpatched advisory arrives, and by then the upgrade is an emergency rather than a maintenance task.

It is also why WordPress’s own guidance can mislead. The requirements page recommends PHP 8.3 or greater, and says WordPress still works on 7.4. Both statements are true. Neither tells a site owner that 8.3 itself has 13 months of security fixes left.

Unsupported is not always unpatched

One honest caveat. When we covered the October PHP security release, we found that Canonical patched seven PHP branches while the PHP project patched four. Debian 12 ships PHP 8.2 and will keep backporting fixes to it under its own LTS programme well beyond December. A server running the distribution’s own PHP package, with unattended upgrades switched on, is in a different position from one running an upstream build.

The problem is that most WordPress sites cannot tell you which of those they are. Shared hosting control panels, Docker’s official php:8.2 images and most managed platforms follow the upstream calendar. Docker’s php:8.1 images stopped updating on 31 December 2025, and the 8.2 images will most likely do the same. If you do not know who builds your PHP binary, assume it is upstream and that the support ends this year.

What to do in the next six weeks

  1. Find out what you actually run. Check Tools, then Site Health, then Info, then Server inside wp-admin. Do not trust the hosting dashboard alone; the panel setting and the version actually serving requests can disagree.
  2. Find out who patches it. A distribution package, a control panel build or a container image. This decides whether 31 December matters to you at all.
  3. Audit plugins and themes before you switch. Clone the site to staging, switch it to the target version and run it with debug logging on. Deprecation notices are not failures, but they tell you which plugins nobody maintains. PHP 8.4 deprecated implicitly nullable parameter types, which old plugins use everywhere.
  4. Replace, do not patch, abandoned plugins. A plugin that has not been updated since 2023 will not be fixed for you. Budget for replacing it now rather than forking it under pressure in February.
  5. Schedule the switch before the freeze. Most hosts let you change PHP version per site in minutes. Doing it in the first week of December leaves time to roll back and fix before the holidays.

Which version to target

Skip 8.3. It gives you one year of security fixes and puts you back in exactly this position next November. PHP 8.4 is the conservative choice: security support until the end of 2028 and two years of plugin authors testing against it. PHP 8.5 buys another year, until the end of 2029, and well-maintained plugins have had a year to catch up, though you should test yours rather than assume. PHP 8.6 is two days old; leave it to the early adopters until the first point releases ship.

For agencies and anyone looking after more than a handful of sites, the lesson from this year’s data is less about PHP 8.2 and more about process. If your upgrades only happen when something breaks, half your estate will be unsupported every January, indefinitely. Put the end-of-life dates for PHP, your database and your Node.js runtime into the maintenance calendar, and move each site one branch at a time on a schedule you choose. We also wrote about how quickly a WordPress vulnerability becomes a real attack, which is the cost of getting this wrong.

Need a hand before the deadline?

REPTILEHAUS runs PHP and WordPress upgrades for clients as a defined piece of work: inventory, staging tests, plugin replacement and a scheduled cut-over with rollback. Our DevOps team also sets up the version monitoring that stops this becoming an annual fire drill. If you have sites still on 8.2 or older, get in touch and we will tell you honestly how much work they need.

Method

Live data from api.wordpress.org/stats/php/1.0/, fetched 21 November 2026. Historical figures from Internet Archive captures of the same endpoint on 10 January, 25 February, 27 September and 2 November 2026. Support dates from php.net and endoflife.date. Shares are percentages of WordPress sites reporting to WordPress.org, not of all websites, and the projection assumes the September to November pace holds.

📷 Photo by Halil Celik on Unsplash