What you need to know
PHP 8.2 receives critical security fixes only until December 31, 2026, and then reaches end of life. Sites and applications still on 8.2, or on already-unsupported branches, need a tested move to 8.3 or later.
Potentially affected
WordPress and other PHP websites, web applications and hosting servers running PHP 8.2 or an earlier branch, including plugins, themes and custom code that must be compatible with a newer branch.
DSE recommendation
DSE recommends finding every site and server still on PHP 8.2 or older and moving each to a supported branch, preferably 8.3 or later as WordPress recommends, before December 31, 2026.
PHP 8.2 receives critical security fixes only until December 31, 2026, and then reaches end of life. Sites and applications still on 8.2, or on already-unsupported branches, need a tested move to 8.3 or later.
Source facts
PHP’s Supported Versions page says each release branch is fully supported for two years from its initial stable release, then supported for two further years for critical security issues only, after which it reaches end of life. Security-only releases are made as needed, so there may be multiple point releases or none.
The page lists security support for PHP 8.2 until December 31, 2026, for 8.3 until December 31, 2027, for 8.4 until December 31, 2028 and for 8.5 until December 31, 2029. It warns that users of an end-of-life release should upgrade as soon as possible because they may be exposed to unpatched security vulnerabilities. A migration guide is published for each supported branch.
For WordPress sites, WordPress.org recommends that hosts support PHP 8.3 or greater, and notes that PHP 7.4, which WordPress still runs on, has reached its official end of life and may expose a site to security vulnerabilities.
Applicability
Use this for managed hosting, shared servers, containers and build images that run PHP. The currently supported list begins at 8.2, so 8.1 and older branches are already past end of life.
DSE recommendation
DSE recommends finding every site and server still on PHP 8.2 or older and moving each to a supported branch, preferably 8.3 or later as WordPress recommends, before December 31, 2026. For each site, list the PHP version, the plugins, themes and libraries in use and their stated PHP compatibility, then read the migration guides for each branch being crossed. Upgrade a staging copy first, fix deprecations and errors, and schedule production changes with a rollback point.
Verification
On each upgraded host, confirm the running version from the server, not only the control panel, and review the PHP error log after typical traffic. Exercise logins, forms, checkout and scheduled tasks on staging before cut-over, and keep a dated record of the version per site.
Official references
PHP.net — Supported Versions. WordPress.org — Requirements. Reviewed October 18, 2026.
Review the official source
PHP.net — Supported Versions · Verified October 18, 2026
Need help applying this guidance safely?
DSE can help confirm applicability, protect service continuity, and validate the result across physical security and IT systems.
Talk with DSE