On Wednesday 18 November 2026 cPanel released a critical security patch for a flaw in the WP Toolkit proxy inside cPanel & WHM. cPanel says successful exploitation allows unauthenticated remote code execution, which may let an attacker take control of the server. Every supported version is affected. A CVE has been requested but not yet assigned.
This is a different class of bug from the September WP Toolkit flaw, CVE-2026-87900, which needed a logged-in cPanel account. Here the attacker needs no account at all, which puts it alongside the April login bypass, CVE-2026-41940, in urgency. Patch today.
Patched builds
| Branch | Fixed in | Released |
|---|---|---|
| 138 | 11.138.0.25 | 18 Nov 2026 |
| 136 | 11.136.0.52 | 18 Nov 2026 |
| 134 | 11.134.0.72 | 18 Nov 2026 |
| 110 | 11.110.0.159 | 18 Nov 2026 |
| WP Squared | 138.1.19 | 18 Nov 2026 |
The per-branch change logs list each of these as a "Targeted Security Release", with no case number or detail. The fix ships in the cPanel & WHM build itself. Unlike CVE-2026-87900, cPanel's notice names no separate WP Toolkit version to install.
Check and update
Automatic updates deliver the patch, but cPanel recommends updating by hand now rather than waiting for the nightly run:
/usr/local/cpanel/cpanel -V
/usr/local/cpanel/scripts/upcp --force
/usr/local/cpanel/cpanel -V
The second version check should show the fixed build for your branch, or later. If upcp stalls or errors out, work through fixing cPanel update failures. Updates only download while the server's cPanel license is active, so check that first if upcp reports a license problem.
Workaround if you cannot update yet
cPanel gives a one-line stop-gap that disables proxying in WP Toolkit. Run it as root:
/usr/local/cpanel/3rdparty/bin/perl -MCpanel::Leika -e 'Cpanel::Leika::set_leika_override("wptk.proxypass", "false")'
The trade-off is small. According to cPanel, it switches off full management of WordPress Security Settings from inside wp-admin. Sites, cPanel, WHM, and the WP Toolkit interfaces inside cPanel keep working as before. Customers who manage WordPress security hardening from the cPanel side won't notice.
cPanel's notice doesn't give a command to undo the override after you patch. Treat the workaround as a bridge to the update, not a substitute for it.
Who is exposed
- Any cPanel & WHM server on a supported branch below the builds above. cPanel does not limit exposure to servers with WordPress sites or active WP Toolkit installs.
- WP Squared servers below 138.1.19.
- Shared and reseller hosts first. An unauthenticated bug reachable over the network is what mass scanners look for once details or a CVE appear. Assume the gap between disclosure and exploitation is days, not weeks.
The flaw was reported by Adam Kues of Assetnote. If you run cPanel and Plesk side by side, note that this advisory covers the cPanel build of WP Toolkit only. See WP Toolkit on cPanel vs Plesk for how the two differ.
Which cPanel version fixes the WP Toolkit proxy vulnerability?+
Is there a CVE for the cPanel WP Toolkit proxy RCE?+
How do I disable the WP Toolkit proxy in cPanel?+
Does updating WP Toolkit fix this cPanel vulnerability?+
Do I need a login to exploit the cPanel WP Toolkit proxy flaw?+
Next steps
- CVE-2026-41940, the cPanel login bypass: the last unauthenticated cPanel flaw, and how it was exploited.
- cPanel 138.0.20 third-party security updates: the build round before this one.
- Fix cPanel update failures: when
upcpwon't reach the patched build.