Check Your WordPress PHP Version Before PHP 8.2 EOL

Zusammenfassung

Pixel shares practical ways to check which PHP version a WordPress site runs, including Site Health and WP-CLI. PHP 8.2 security support ends on December 31, 2026, and some hosts may remove it earlier, so checking your version helps you plan a timely upgrade.

DEV Community

Find out which PHP version your WordPress site runs before PHP 8.2 support ends

PHP 8.2 reaches end of life on 31 December 2026 — that is the day the PHP project stops shipping security fixes for it. Your WordPress site will not go dark the next morning, but php.net's own wording for an end-of-life release is that users "may be exposed to unpatched security vulnerabilities" and "should upgrade as soon as possible." You may also have less time than the calendar suggests. One hosting platform, WP Cloud, removes PHP 8.2 on 15 December 2026, ahead of the official date. As developer Bo Zeng put it in a dev.to write-up on running WordPress plugins on PHP 8.4, "the hosting company is going to move you to 8.3 or 8.4 sooner or later." So the first step is simple: find out which PHP version your site runs. About 22% of WordPress sites reporting their version to WordPress.org are on 8.2, with roughly 14% still on 7.4 and 9% on 8.1. Here are three ways to check yours, fastest first. 1. WP Admin → Tools → Site Health → Info → Server No code needed. Log in to your WordPress dashboard. Open Tools → Site Health → Info. Expand the Server section. Per the WordPress documentation, it "shows information about your server architecture, web server, various PHP variables" — including the PHP version. Then check the Status tab on the same screen. If WordPress considers your PHP outdated, it shows a security item: "Your site is running an outdated version of PHP, which requires an update." Write the number down. If it reads 7.4, 8.0 or 8.1, you are already on an end-of-life version that WordPress supports "for backward compatibility only," and the rest of this applies with more urgency. One caveat: knowing the version does not mean you can change it. WordPress notes that "you may need to contact your hosting provider, as these configurations are often restricted or managed at the server level." AI-generated illustration. 2. WP-CLI If you have SSH access and WP-CLI installed, run this from the site's root directory (where wp-config.php lives): wp --info
It prints the environment, including the PHP version. To get just the version number: wp eval 'echo PHP_VERSION;'

8.2.15

  1. From outside: read X-Powered-By with a small Python script No WordPress login at all? Some servers announce PHP in the X-Powered-By response header. This script checks it using only the Python standard library: #!/usr/bin/env python3
    """Print the X-Powered-By header of a site (often reveals the PHP version)."""
    import sys
    from urllib.request import Request, urlopen

def powered_by(url: str) -> str:
req = Request(url, headers={"User-Agent": "php-version-check/1.0"})
with urlopen(req, timeout=10) as resp:
return resp.headers.get("X-Powered-By", "")

if name == "main":
url = sys.argv[1] if len(sys.argv) > 1 else input("URL: ").strip()
value = powered_by(url)
print(value or "(no X-Powered-By header — this host hides it)")
python3 check_php.py https://your-site.example
Be aware that many hosts deliberately strip or hide this header, so a blank result tells you nothing either way. In that case, fall back to Site Health or ask the host directly. What tends to break on upgrade Knowing your version is step one. Here is what actually fails when PHP moves up, drawn from Zeng's public scan of two real plugins — an events plugin with 50 PHP files and a social feed plugin with 46: WordPress core is rarely the problem. Core has been compatible with PHP 8.3 since WordPress 6.4 and with 8.4 since 6.7. The catch, in the same documentation, is that WordPress "is rarely used in isolation (without any theme or plugins)" — themes and plugins are where upgrades break. Failures are quiet, not white screens. The events plugin produced zero fatal errors, but 17 items that can fail on unexpected input and 5 deprecation warnings. Date handling. Since PHP 8.3, DateTime::modify() throws a DateMalformedStringException when it can't parse the string, instead of failing quietly. Dynamic properties. A pattern older plugin code uses everywhere, de...
Check Your WordPress PHP Version Before PHP 8.2 EOL
Powered by Readybot.io

Das Neueste von Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …