PHP2Shell: How We Patched Older PHP Versions with CloudLinux

Last verified: October 31, 2026.

The October 2026 PHP security vulnerabilities known as PHP2Shell are tracked as CVE-2026-109618 and CVE-2026-109619. We installed CloudLinux's patched PHP packages on Royal 2 on October 21, including fixes for older PHP branches offered through CloudLinux PHP Selector.

What was the vulnerability?

These were two critical flaws in PHP itself that could allow an unauthenticated attacker to execute code through specially crafted web requests. They were not limited to WordPress or a particular plugin. Updating a website's plugins alone does not replace the required PHP runtime fix.

The PHP project's fixed releases for supported branches were PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12. Older branches required vendor-supplied fixes rather than a new release from the PHP project.

How did we patch older PHP versions with CloudLinux?

CloudLinux maintains security-patched PHP packages, including older branches, through its alt-PHP and HardenedPHP technology. Its engineers backport security fixes: they adapt the fix to an older PHP branch without requiring the application to move immediately to a different major version.

For Royal 2, we installed the CloudLinux package updates for the available PHP branches, including legacy versions from PHP 5.2 through PHP 8.1 and the newer PHP 8.2 through 8.5 branches. This addressed these vulnerabilities while retaining customers' selected PHP branches for application compatibility.

Our October 31 verification checked the installed package records and changelogs. For example:

  • PHP 7.4: alt-php74-common-7.4.33-81.el9 lists fixes for both CVE-2026-109618 and CVE-2026-109619.
  • PHP 8.2: alt-php82-common-8.2.34-7.el9 also lists fixes for both CVEs, even though PHP itself still reports version 8.2.34.

Why does my PHP version still look old?

The PHP version and the vendor's package release are different identifiers. A backported fix can change the package release while leaving the PHP version displayed by your application unchanged.

For example, CloudLinux's patched PHP 7.4 package still reports 7.4.33. That does not mean the security update is missing. The package release and its security changelog are needed to assess whether a specific vulnerability has been fixed.

A scanner that checks only the displayed PHP version may therefore flag a patched build. However, do not dismiss every scanner warning as a false positive. Send us the affected domain, CVE number and full scan result so we can check the actual PHP runtime and package serving your site.

Does this mean old PHP is fully supported again?

No. CloudLinux's backported fixes do not return an end-of-life branch to official PHP project support. These updates address the listed vulnerabilities; they are not a guarantee against every current or future security issue.

We still recommend testing your application on a currently supported PHP branch and updating it when compatible. Do not switch a production site blindly if its theme, plugins or custom code depend on an older version. See How to Change the PHP Version via CloudLinux Selector in DirectAdmin.

Do I need to install the server patch myself?

If your website uses our CloudLinux-managed PHP on Royal 2, we manage the server PHP packages. You do not need to upload a patch into your website or change PHP versions solely to receive this backported fix.

This does not automatically cover a self-managed VPS, a custom PHP binary, a container or another server. Those runtimes must be checked and updated separately. If you are unsure which runtime your site uses, open a support ticket.

Are firewall rules enough?

No. Imunify360 WAF rules can block known exploit patterns, but they are an additional layer, not a replacement for patched PHP packages. Likewise, installing the patch does not remove malware or undo an earlier compromise. If you notice unexpected files, redirects or account activity, contact support for investigation.

Sources and further reading

  • 0 Utilisateurs l'ont trouvée utile
Cette réponse était-elle pertinente ?

Articles connexes

How to Disable Directory Browsing Using the htaccess Rule

For security purposes, you should disable directory browsing on your website so no one can see...

How to Protect the htaccess File

You can prevent unauthorized access to your htaccess file by adding this rule to the file: #...

How to Block Any IP Address via an htaccess Rule

If you want to block an IP Address, you can add the below lines to your htaccess file. order...

How to Restrict Access to Directories by IP Address

To secure your admin area from hackers, you should only allow access to your admin directory from...

How to Change the PHP Version via CloudLinux Selector in DirectAdmin

  You can use CloudLinux's Select PHP Version to change your website's PHP Version in...