Critical: cPanel WP Toolkit Proxy Remote Code Execution + PHP CVE-2026-115560 — How to Patch (November 2026)
Two security fixes landed this week and both matter on a typical cPanel server:
- cPanel & WHM — WP Toolkit proxy (published 18 November 2026). An attacker who is not logged in can run code on the server and take control of it. This is fixed by updating cPanel & WHM.
- PHP — CVE-2026-115560 (fixed 19 November 2026). This is the PHP session flaw reported on 23 October, when no fix existed yet. A session serializer mismatch can lead to remote code execution. It is fixed in PHP 8.2.36, 8.3.37, 8.4.28 and 8.5.13.
Both updates are safe to run on a production server. Sites stay online during the work, which takes about 15–20 minutes.
Using Plesk or DirectAdmin? Part 1 does not apply to you. Go straight to Part 2 below.
Part 1 — cPanel & WHM: WP Toolkit proxy vulnerability
Step 1 — Check your cPanel version
Run as root:
cat /usr/local/cpanel/versionThe second number is your release tier. For example, 11.134.0.58 is tier 134, build 58. You are protected if your build is at least:
| Release tier | Safe build (or later) |
|---|---|
| 110 | 11.110.0.159 |
| 134 | 11.134.0.72 |
| 136 | 11.136.0.52 |
| 138 | 11.138.0.25 |
| WP Squared | 11.138.1.19 |
If your tier is not in this table (for example 126 or 132), there is no fixed build for it. Open a ticket before you update and we'll tell you which supported tier to move to.
Step 2 — Update cPanel & WHM
tslzCP ; /scripts/upcp --forceThe first command refreshes your cPanel licence, so the update runs against an active licence. The second forces the update, which usually takes 5–15 minutes.
WP Squared servers: run
/scripts/upcp --forceWhen the update finishes, run the Step 1 check again. Your build must now match the table or be newer.
Part 2 — PHP CVE-2026-115560
Step 1 — See which PHP builds you have
cPanel (EasyApache PHP):
rpm -qa 'ea-php*-php-common' | sort
CloudLinux PHP Selector (alt-php):
rpm -qa 'alt-php*-common' | sort
You are protected when every version you use is at least:
| PHP branch | Fixed version |
|---|---|
| 8.2 | 8.2.36 |
| 8.3 | 8.3.37 |
| 8.4 | 8.4.28 |
| 8.5 | 8.5.13 |
Step 2 — Update PHP
cPanel:
yum update 'ea-php*'
/scripts/restartsrv_apache_php_fpm
/scripts/restartsrv_httpdOn LiteSpeed servers, also run
/usr/local/lsws/bin/lswsctrl restartrestartsrv_apache_php_fpm reports a failure on a LiteSpeed-only server, that is expected (LiteSpeed does not use PHP-FPM) and your sites keep running.
CloudLinux alt-php: run
yum update 'alt-php*'Plesk: update PHP from Tools & Settings » Updates, or run:
plesk installer --select-release-current --upgrade-installed-components
DirectAdmin:
cd /usr/local/directadmin/custombuild && ./build update && ./build phpRun the Step 1 check again afterwards.
Step 3 — If you can't update yet (or you run PHP 7.4, 8.0 or 8.1)
PHP 7.4, 8.0 and 8.1 are end-of-life and get no fix from PHP itself. On CloudLinux they get fixes through Extended Lifecycle Support, which is included with your CloudLinux licence:
tslzCLN --tuxcare
yum update 'alt-php*'Until a fixed build is installed for every version you use, turn off session upload progress. This is the PHP project's own interim advice. In each PHP version's php.ini (on cPanel: WHM » MultiPHP INI Editor), set:
session.upload_progress.enabled = Off
Then restart PHP as in Step 2. Very few sites use this feature. It only shows upload-progress bars for PHP's built-in session handling.
More current advisories
Our Server Security Advisories page lists other issues affecting cPanel, CloudLinux and LiteSpeed servers, including the earlier PHP CVE-2026-109618 & CVE-2026-109619 patch guide.
Managed-service customers
If your server is on one of our Server Management plans, we apply these updates for you. Open a ticket if you'd like confirmation for your server. Not on a plan and would rather we did it? Open a ticket, share access, and we'll update cPanel and PHP and check both.