Every WordPress site depends on software its owner never sees. Beneath the themes and plugins sits PHP, the programming language WordPress is written in. Each version of PHP is maintained for a fixed period that ends on a published date, yet most WordPress sites run a version whose period has ended or ends this year.

PHP 8.2 reaches end of life on December 31, 2026, according to the PHP project’s schedule. WordPress.org’s statistics for November 13 show about 22% of WordPress sites on version 8.2 and another 32% on versions the PHP project has already stopped fixing.

Each PHP Version Runs on a Published Calendar

The PHP project publishes the date each version's support ends, years ahead.

The PHP project supports each version for four years. For the first two it fixes bugs and security issues, and for the last two only critical security issues. After that the version reaches end of life, which the project describes as “a release that is no longer supported,” whose users “may be exposed to unpatched security vulnerabilities.”

Version Support ends Sites
Below 7.4 2021 or earlier 5%
7.4 Nov 2022 14%
8.0 Nov 2023 3%
8.1 Dec 2025 9%
8.2 Dec 31, 2026 22%
8.3 Dec 31, 2027 28%
8.4 Dec 31, 2028 11%
8.5 Dec 31, 2029 7%

The last column is the share of WordPress sites on each version, from WordPress.org’s figures for November 13, 2026, rounded. The dates are the PHP project’s, including those for versions already expired.

Nothing visible happens on January 1. A site on version 8.2 keeps running, without further security fixes from the PHP project. The date that can break a site is the host’s own. WP Cloud, a WordPress hosting platform, will remove version 8.2 on December 15, 2026, two weeks before the PHP project’s date.

More Than Half of WordPress Sites Are Affected

More than half of WordPress sites run PHP 8.2 or a version whose support has already ended.

WordPress does not force the upgrade. It still works with PHP 7.4, while its hosting team recommends version 8.4 or 8.5 for new installations. The delay usually lies in a plugin or theme that was never tested on a newer version, or in a hosting account that nobody has opened since the site launched.

PHP is also only part of what has to be kept current. Patchstack, a WordPress security firm, found 91% of the vulnerabilities reported in the WordPress ecosystem in 2025 in plugins.

October Showed What End of Life Means

In October 2026 two critical flaws received corrected releases only for the versions still supported.

In October 2026 the PHP project disclosed two critical flaws, reported in the press as PHP2Shell, that could let an attacker run code on a web server without logging in. It released corrected editions of versions 8.2, 8.3, 8.4 and 8.5. Five days later the US Cybersecurity and Infrastructure Security Agency added both to its catalog of vulnerabilities known to be exploited and gave federal agencies three days to respond.

For version 8.1 and older the project issued no release. Citing the severity, its security team published source patches for versions 7.4, 8.0 and 8.1 and told users to check with their vendors. Ubuntu, a widely used server operating system, shipped the fix for its edition of PHP 8.1. Nothing was published for versions older than 7.4.

On an expired version, a fix depends on someone outside the PHP project choosing to supply it, and on the host installing it. Neither is visible from the website.

A supported version is not protection by itself either. Every release of versions 8.3, 8.4 and 8.5 from before October 21 carried the same two flaws, and the fix arrived as releases 8.3.36, 8.4.27 and 8.5.12.

The Request to the Host Has Three Parts

The host can confirm the exact version, who upgrades it and how fast security releases are installed.

A firm can settle where it stands by asking its hosting company, or whoever maintains the site, three things.

  • The exact version. WordPress shows it under Tools, Site Health, Info, then Server, as a full number such as 8.3.36.
  • Who upgrades it. Some hosts move every site on a set date, some charge to keep an expired version running, and some leave the setting wherever the customer last put it.
  • How fast security releases are installed. October’s fix reached a site only when its host installed it.

The Upgrade Is a Setting, and the Work Is in the Testing

Version 8.4 is supported until the end of 2028, so one move to it covers two deadlines.

The upgrade itself is a setting in the hosting account. Version 8.4 is supported until the end of 2028, so one move to it covers two deadlines, where a move to 8.3 buys a single year.

The work lies in confirming that the site still functions. The site should be backed up, then copied to a staging area, a private duplicate, and switched there first. A fault on a new PHP version appears only when the affected code runs, so every form should be submitted and the error log read. Where a host offers no staging tool, a full backup and the ability to switch the setting back serve the same purpose.

A site left untouched for several years usually needs its plugins and theme updated before the switch, which is work a firm can schedule.

The Date Returns Every Year

A version of PHP reaches end of life every year, and PHP 8.3 follows on December 31, 2027.

December 31, 2026 is one date in a series. A version of PHP reaches end of life every year, and a new one arrives late each year.

A calendar covers only the dates that are published. October’s flaws were not on one, and neither were the security releases WordPress issued in 2026, one of them serious enough that WordPress.org forced the update onto affected sites. Open source software gives a firm ownership of its website, and ownership carries a cost: someone has to keep the software current.

Firms that give the published dates an owner, and confirm how fast their host installs the fixes that arrive unannounced, will meet both as routine work.