Skip to content

PHP version strategy on cPanel — which versions to support, when to retire

How to manage PHP versions across a multi-tenant cPanel fleet, when to retire end-of-life versions, and how to communicate forced upgrades to customers.

PHP versions are the most common source of inherited cPanel ugliness. A tenant running PHP 5.6 in 2026 is not just on an unsupported language version — they’re a CVE waiting to be exploited, and the moment they’re compromised, the blast radius is the whole shared host. PHP version policy is therefore both a security policy and a customer-communication policy.

The trade-off

Aggressive deprecation forces customers to update their code, costs them time, generates support tickets, but reduces your attack surface. Permissive policy keeps customers happy short-term but leaves you carrying CVE exposure that the PHP project itself no longer patches.

CloudLinux PHP Selector with hardened-PHP (Alt-PHP) extends support for old versions past their upstream EOL with backported security patches. That buys you time but doesn’t change the underlying truth: code on PHP 5.6 in 2026 is also code on a framework version, a CMS version, and a set of dependencies that nobody has patched in years.

How to decide — the support matrix

In 2026 a reasonable cPanel host’s PHP support matrix:

VersionStatusAction
PHP 5.6, 7.0, 7.1EOL upstream + hardened-PHP availableAvailable only as paid migration assistance, sunset within 12 months
PHP 7.2, 7.3, 7.4EOL upstream + hardened-PHP availableAvailable with deprecation notice, sunset within 18 months
PHP 8.0EOL upstreamMigrate; 6-month grace period
PHP 8.1, 8.2Security-supported upstreamStandard option
PHP 8.3, 8.4Active upstreamDefault for new accounts
PHP 8.5+Beta / latestAvailable for those who ask

Specific dates depend on cPanel’s CloudLinux/PHP support matrix and your own commitments.

What to do

  1. Publish a PHP version policy with explicit sunset dates per version. Don’t promise versions you can’t keep.
  2. Track which accounts run which PHP version. WHM > MultiPHP Manager makes this visible per domain.
  3. Notify customers running EOL versions on a predictable schedule — 90 days before sunset, 30 days, 7 days, then move them.
  4. Default new accounts to a security-supported version (PHP 8.3 in 2026). Don’t default to “latest” — wait until the version has been out 6 months and CMS ecosystems support it.
  5. Provide a sandbox path. Customers should be able to test their site on a newer PHP before being forced.
  6. Force-migrate at the published date. Customers who didn’t act will need support but the announcement preceded the action.
  7. Document compatibility — common breakages like deprecated mysql_* functions, removed each(), stricter type juggling.

Stack Harbor manages PHP version policy and the customer communication as part of cPanel server management.