The cPanel WP Toolkit proxy vulnerability affects supported prepatch cPanel & WHM builds, according to cPanel’s November 18 advisory. The fixed thresholds are 110.0.159, 134.0.72, 136.0.52, 138.0.25, and WP2 138.1.19 for their respective tracks. Successful exploitation can allow unauthenticated remote code execution and may let an attacker take control of the server.
Germany’s BSI rates the issue high and describes an anonymous remote attacker who could execute code. Treat exposed hosting control planes as a patch priority and record their installed builds. A vulnerability intelligence platform can help place this advisory alongside the rest of the patch queue.
Which Versions Fix the cPanel WP Toolkit Proxy Vulnerability?
cPanel marks all supported tracks as affected and provides five patched release thresholds. Match the installed branch before selecting a target release. The table follows cPanel’s current public notice, including the 138.0 branch missing from BSI’s product tree.
| cPanel & WHM branch | Patched version in cPanel’s advisory |
|---|---|
| 110 | 110.0.159 or later |
| 134 | 134.0.72 or later |
| 136 | 136.0.52 or later |
| 138.0 | 138.0.25 or later |
| WP2 138.1 | 138.1.19 |
The WP2 row is labeled separately in the vendor’s table, so verify the exact installed track. After the update, confirm the running build rather than relying only on a completed maintenance job. Keep each server’s result in the patch management record.
What Risk Does the Proxy Vulnerability Create?
cPanel identifies the affected component as the WP Toolkit proxy and describes the possible impact as unauthenticated remote code execution. The vendor says successful exploitation may allow server takeover; it does not describe a root cause or attack sequence in this notice. BSI’s November 18 record likewise states that an anonymous remote attacker could execute arbitrary code.
Brandefense Blackhole counted 14,080 dark-chat posts matching the broad term “cPanel” from August 21 through November 19, 2026. The unit is matching posts, not unique actors or servers. This broad count does not establish discussion of this particular flaw or its exploitation.
The public advisories do not give this issue a CVE identifier, so match inventory and tickets by the vendor advisory and BSI reference WID-SEC-W-2026-4671. Avoid treating a different cPanel CVE as the same flaw. The vulnerability management guide can help connect affected assets with patch owners.
What Should cPanel Administrators Do Now?
Begin with the supported cPanel & WHM installations you operate, especially systems whose control plane is reachable from untrusted networks. cPanel’s instruction is to update to a patched version. Our operational sequence below adds build verification and an evidence review around that vendor instruction.
- Inventory installationsRecord each server, cPanel & WHM track, WP Toolkit version, and patch owner.
- Apply the matching fixUpdate each branch to the vendor-listed patched release or a later supported build.
- Verify the resultConfirm the running version on every server and record failed or deferred changes.
- Review suspicious activityPreserve relevant web, control-panel, process, and authentication records for investigation.
If logs suggest unauthorized access, investigate the affected server as an incident and preserve evidence before changing more settings. Patching the vulnerable component does not resolve any access an intruder may already have gained. Use the incident response plan template to assign investigation and recovery work.
What If a Full cPanel Update Must Wait?
cPanel’s updated mitigation says to upgrade WP Toolkit to version 6.11.8 if a patched cPanel release cannot yet be installed. That is the vendor’s interim recommendation; schedule the matching cPanel & WHM update as the final patch decision. Confirm the WP Toolkit version after applying the interim change.
Record why a full update is delayed, who owns it, and when the installed build will be checked again. Recheck cPanel’s public advisory before rollout because its mitigation guidance changed after the initial source capture.
Frequently Asked Questions
Which cPanel & WHM releases contain the fix?
cPanel lists 110.0.159, 134.0.72, 136.0.52, and 138.0.25 or later for their tracks, plus WP2 138.1.19.
Can the WP Toolkit proxy flaw be exploited without authentication?
cPanel says successful exploitation can allow unauthenticated remote code execution and may let an attacker take control of the server.
What does cPanel recommend when a full update is delayed?
The current cPanel advisory recommends updating WP Toolkit to 6.11.8. Administrators should still plan the matching patched cPanel & WHM release.
