· via dev.to (home feed)
PHP 8.2 hits end of life on 31 December 2026 with about 22% of WordPress sites still on it
PHP 8.2 stops receiving security fixes on 31 December 2026, and roughly 22% of WordPress sites that report their version still run it. A dev.to guide explains how to check and what typically breaks on upgrade.

The clock runs out on 31 December 2026
PHP 8.2 reaches end of life on 31 December 2026, the day the PHP project stops shipping security fixes for the release. According to a dev.to write-up from the Gigzman agency, WordPress sites will not stop working overnight, but php.net's guidance for end-of-life releases is unambiguous: anyone still on one risks security holes that will never be patched and should move to a supported version quickly.
Some hosts will force the issue early. The article notes that the hosting platform WP Cloud removes PHP 8.2 on 15 December 2026, two weeks ahead of the official date. Developer Bo Zeng, whose plugin compatibility testing the piece draws on, observes that one way or another, hosts will eventually move customers to PHP 8.3 or 8.4.
The numbers make the deadline more than theoretical. Among WordPress sites that report their version back to WordPress.org, roughly 22% run PHP 8.2, while about 14% are still on PHP 7.4 and 9% on 8.1 — versions already past end of life, which WordPress keeps working with only so older sites keep functioning.
Three ways to find out what you run
The article lists three checks, fastest first:
- No code needed. In the WordPress dashboard, Tools → Site Health → Info → Server shows the PHP version alongside other server details, and the Status tab raises a warning item when WordPress considers the installed PHP outdated.
- With SSH access and WP-CLI installed, running
wp --infofrom the site root prints the environment including the PHP version;wp eval 'echo PHP_VERSION;'returns just the number. - From outside, some servers disclose the version in the X-Powered-By response header, which a short Python script using only the standard library can read. Many hosts strip that header deliberately, so a blank result proves nothing — fall back to Site Health or ask the host directly.
One caveat the article stresses: knowing the version does not mean you can change it. PHP selection is usually restricted or managed at the server level by the hosting provider.
Core is fine; plugins are the problem
WordPress core has supported PHP 8.3 since version 6.4 and PHP 8.4 since 6.7. The real friction is in themes and plugins — WordPress, as its own documentation notes, is rarely used without them.
Zeng's testing, cited throughout the article, scanned two real plugins: an events plugin with 50 PHP files and a social feed plugin with 46. The results were not dramatic but insidious. The events plugin produced zero fatal errors, yet 17 places that can fail on unexpected input and five deprecation warnings. Failures are quiet rather than white screens.
Specific pain points include date handling — since PHP 8.3, DateTime::modify() throws a DateMalformedStringException on strings it cannot parse instead of failing silently — plus dynamic properties, a pattern common in older plugin code that was deprecated in PHP 8.2. The social feed plugin runs on PHP 8.4 but logs a deprecation warning that will keep filling the error log until it turns into a break in a later version. Some changes are subtler still: PHP 8.3's migration notes cover how assigning a negative index to an empty array changes the index that comes next.
Fixing this is judgment work, not search-and-replace. Zeng declined to auto-apply one fix because it would have traded a deprecation notice on PHP 8.4 for a parse error on PHP 7.0, and on date handling he argues the correct fallback is a human decision, not something to automate.
Stage it before you ship it
The recommended order of operations, per the article: take a full backup of files and database, copy the site to staging, update WordPress core, the theme and every plugin there, switch staging to the target PHP version, and fix what the error log and a code scan flag. Then click through forms, checkout, search and logins on the new version before touching production, and keep watching the error log for a few days after the live switch.
WordPress recommends PHP 8.3 or greater, and its hosting handbook points to 8.4 or later for production. PHP 8.3 receives security fixes until 31 December 2027 and PHP 8.4 until 31 December 2028, so either target buys breathing room.
Why it matters
Roughly a fifth of reporting WordPress sites are weeks away from running a PHP release with no security patches, and a further large share is already on dead versions. Because most breakage appears as deprecation warnings and quiet behaviour changes rather than crashes, sites can look healthy while accumulating problems that become outages on a later upgrade. The practical deadline is not even 31 December — hosts such as WP Cloud start moving customers in mid-December, which leaves only a few weeks for a staged, properly tested migration.
- #php
- #wordpress
- #security
- #end-of-life
- #web-development