Merchlint
Available now
Next, in this order
  • DeutschDE
  • EspañolES
  • FrançaisFR
  • ItalianoIT
  • PortuguêsPT
  • NederlandsNL
  • SvenskaSV
  • TürkçeTR

A language shows up here once its pages are actually written. Nothing on this site is machine-translated, except a few German and Spanish pages that no native speaker has reviewed yet.

Install free Install
← All checks

Unsupported PHP, WordPress or WooCommerce

Software past its support window stops receiving security fixes. Nothing about the store changes on that day, which is exactly why it goes unnoticed for years.

Group
Environment
Confidence
H — heuristic
Name on the plugin screen
Unsupported versions
Included in
the free plugin
Updated
Code
E1

The symptom

There isn’t one. A PHP release does not stop working on the day its support ends; it keeps serving pages exactly as it did the day before.

You find out by accident. A plugin update refuses to install because it requires a newer PHP. A payment gateway sends a notice about a minimum version. A developer looks at the site and asks a question in a certain tone. By then the version has usually been out of support for a couple of years.

What it costs

Security fixes stop. That is the whole problem, and it is enough. PHP 7.4 stopped receiving security support on November 28, 2022. A vulnerability found in it after that date never gets an official fix, and nobody tells you, because nobody maintains that version anymore.

Everything else follows from that:

  • Plugins and themes move on. Their authors raise their minimum requirements, and at some point an update you need refuses to install. That is usually the moment the upgrade becomes urgent rather than sensible, which is the worst time to do it.
  • You miss out on free speed. Newer PHP runs the same code substantially faster than 7.x—on a store, every page responds sooner, with no other change.
  • Payment and shipping integrations set their own minimum versions. They are the least willing to support old PHP, for obvious reasons.

WooCommerce works the same way. It fixes critical vulnerabilities (rated 9 or higher out of 10 on the CVSS scale) in its last 21 releases, about two years; on 11.2 that reaches back to 9.2. Other fixes go only into the newest release, and an older release gets no security fixes at all. WordPress publishes no end dates and tells you to run the latest version.

The next dates (checked on October 27, 2026):

  • PHP 8.1 has had no security fixes since December 31, 2025.
  • PHP 8.2 gets its last security fixes on December 31, 2026. Almost a quarter of WordPress sites run it, and another third run something older (wordpress.org statistics, October 2026). The date is already in Merchlint’s table: from November 1, 2026, the check reports PHP 8.2 in advance, marked “worth checking”, and from January 1, 2027 as unsupported.
  • WooCommerce 11.6, planned for February 2027, will require PHP 8.1 or newer. WooCommerce 11.3 will show a dismissible notice about it in the admin of stores still running PHP 7.4 or 8.0. On those stores, WordPress will not install 11.6 at all, so they stay on an older WooCommerce.

Sources: php.net, supported versions and the WooCommerce developer blog, New Requirement for WooCommerce 11.6: PHP 8.1.

How to check it yourself

wp cli info | grep "PHP version"
wp core version
wp plugin get woocommerce --field=version

Then compare each version with what its maker publishes. php.net lists the supported PHP versions and their end dates, and WooCommerce publishes its security window (the 21 releases above). WordPress publishes no end dates, so the safe answer there is the latest version.

For PHP, php -v on the command line is not necessarily the version your site runs: many hosts use one PHP for the command line and another for the web server. wp cli info reports the command-line one too. The value that matters is the version your web server uses, which you can read in the WordPress admin under Tools → Site Health → Info → Server.

How to fix it

  1. PHP first. It is the largest gain and usually the smallest task—with most hosts it is a dropdown in the control panel.
  2. On a staging copy, never on production. Switch the version there, click through the store, place a test order, and watch the error log rather than the screen. Fatal errors from an incompatible plugin are loud and immediate; deprecation warnings are quiet and go to the log.
  3. Update WordPress and WooCommerce in that order, and take a backup you have actually restored at least once.
  4. If a plugin blocks the upgrade, that is the finding, not the PHP version. An abandoned plugin holding a whole store on an unsupported PHP is a decision waiting to be made. (The opposite case, a plugin that needs newer PHP than you run, is a check being prepared for the Pro add-on.)

When it’s a false alarm

  • Hosts that backport security patches. Some Linux distributions and managed hosts keep patching a PHP version after the PHP project has stopped. The version number cannot tell you this—only your host can. If that is your situation, the finding is about the version number, not about your actual risk.
  • A version that went out of support last week. Real, but not urgent. The check reports the fact; the urgency is yours to judge.
  • Deliberately pinned versions during a migration or a certification process.

How Merchlint finds it

Merchlint reads the PHP, WordPress and WooCommerce versions your store runs.

PHP is compared against a table of end dates shipped inside the plugin. Merchlint cannot look the dates up: it connects nowhere except up to three of the store’s own product pages, so it cannot ask php.net anything. The table travels with the release and is updated when the plugin is updated. PHP announces its end dates years ahead, so even an older table has the right dates for the versions it lists. What an old table can miss is a date PHP changed after the release, and a PHP version newer than the table, which the check skips.

For WordPress and WooCommerce, Merchlint takes the newest version from the update check WordPress already runs on its own. WooCommerce is counted in releases behind the newest one, across major versions (10.0 follows 9.9). WordPress older than the newest release is reported as “worth checking”, because older WordPress versions often still get security fixes, so being behind does not prove it is unsupported.

Some findings come early, also marked “worth checking”: PHP 60 days before its security fixes end, and WooCommerce on the oldest release still inside the 21-release window, because the next release pushes it out. WordPress publishes no end dates for its versions, so it gets no advance warning.

A PHP version already past its end date, or a WooCommerce more than 20 releases behind, is reported as a fact. This page marks the check H—heuristic because of the “worth checking” findings and because of the table: a check that depends on something that can age should say so rather than present itself as certainty.

The finding shows each version read and what it was compared against: for PHP, the end date and the date of the table; for WooCommerce, the newest release and how many releases behind yours is; for WordPress, the newest release.

Run this check on your store

Doesn't match what you see in your store? Email us—we read every message. contact@merchlint.com