cPanel WP Toolkit Proxy: Unauth RCE - Floor 138.0.25 / Toolkit 6.11.8

cPanel's 18 November 2026 security article is titled Security: Vulnerability in cPanel & WHM's WP Toolkit Proxy - November 18, 2026. Situation line: a security vulnerability affecting cPanel's WP Toolkit proxy. Impact, verbatim: successful exploitation can allow unauthenticated remote code execution, which may allow an attacker to take control of the server.[1]
No CVE ID is on that article. No CVSS. No CWE. No finder credit. No exploitation status. Created 2026-11-18T19:33:56Z, last updated 2026-11-19T16:30:29Z. Match tickets to the Zendesk ID 45133380394135, not to last month's WP Toolkit CVEs.[1]
Patched cPanel & WHM builds in the vendor table: 110.0.159, 134.0.72, 136.0.52, 138.0.25 or later, and WP2: 138.1.19. Affected column: All Supported Versions.[1]
The 138 changelog lists 138.0.25 as 2026-11-18, one bullet: [Security] Targeted Security Release. Same TSR label, same date, on 136.0.52 and 134.0.72.[2][3][4]
110.0.159 is the LTS row of that same 18 November TSR.[5]
Release notes row cPanel & WHM Security Update - November 18 names those four builds and does not list WP Squared - the WP2 floor is only in the security article.[1][6]
This is not on CISA KEV. Catalog 2026.11.18, 1,786 entries, dateReleased 2026-11-18T19:17:41.0354Z. An ID-less vendor bulletin cannot appear there. NVD keyword search for cPanel WP Toolkit in November 2026 returned 0 results this morning.[8][9]
If you run shared or reseller cPanel, this is today's version floor.
What it is
Vendor-published facts, and nothing past them:[1]
- Component named: WP Toolkit proxy inside cPanel & WHM.
- Impact named: unauthenticated remote code execution, possible server control.
- Fix named: the cPanel & WHM builds in the table. Interim: WP Toolkit 6.11.8 if you cannot
upcpyet.
We did not reverse the proxy, map a URL, or send a request. There is no public CWE, gadget, or parameter name on the article. Do not paste a "how it works" paragraph into a customer ticket.[1]
This is not:
- CVE-2026-87900 (22 Sep) - WP Toolkit database-create, authenticated cPanel user, floor 6.11.3.
- CVE-2026-93699 (1 Oct) - WP Toolkit handler, still account-to-account, floor 6.11.4.
- CVE-2026-105476 (26 Oct / posted 6 Nov) - reseller → root file write, floor 138.0.19. Different bug, older floor.
- WordPress core CVE-2026-119977 / 7.1.4 upgrade-window RCE (KEV 3 Nov). Patching WordPress does not patch the panel proxy.
- Yesterday's CVE-2026-14492
local-syncplugin. Uninstalling a plugin does not raisecpanel -V.
The September/October WP Toolkit CVEs needed a cPanel login (PR:L on those CNAs). This bulletin's impact sentence is unauthenticated. That is the whole difference that matters on a shared box. We are not claiming the root cause is the same code path - only that the named surface is again WP Toolkit's proxy layer.[1]
How serious is it?
cPanel wrote unauthenticated RCE and take control of the server. That is a panel-level claim, not a WordPress-plugin claim. On shared hosting the process that talks to every tenant's WP Toolkit is the one you patch.[1]
What the vendor did not write:
- Actively exploited / not exploited.
- CVSS.
- Whether WP Toolkit must be installed, or a WordPress site must exist, for the proxy to be reachable.
- Whether the code runs as
rootor as the WP Toolkit user.
Treat "unauth RCE on the panel" as patch today. Do not wait for a CVE number, a KEV row, or a blog PoC. Absence from KEV is not "safe." It is "no CVE to list."[8]
138.0.27 and 138.0.28 are separate 19 November TSRs on the 138 changelog. 136.0.53 / 136.0.54, 134.0.74, 110.0.161 likewise. Do not flatten those into this advisory.[2][3][4]
The floor for this article remains 138.0.25 (and the sibling trains). Being on 138.0.28 still satisfies ≥ 138.0.25; being on 138.0.24 does not.[2][5]
Who is affected
In scope, per the vendor table:[1]
- cPanel & WHM, all supported versions, until you hit the patched build on your train.
- WP Squared until 138.1.19.
Out of scope unless you have a separate advisory:
- Plesk's WP Toolkit. This article is cPanel's WP Toolkit proxy. The installer URL happens to live on
wp-toolkit.plesk.com; that is how WebPros ships the cPanel package, not a Plesk CVE. - EOL cPanel trains WebPros no longer ships. There is no 102.x / 126.x row in the table.
We did not get a WP Squared changelog (the wp-squared-change-log and 138.1-change-log docs URLs 404'd). The 138.1.19 number is the security article's, only.[1]
What to do now
- Read the build, not the major. As root:
/usr/local/cpanel/cpanel -V
Compare to the floor for your train. 138.0.24 is still below 138.0.25. 110.0.158 is still below 110.0.159.
- Patch cPanel. Vendor call to action is the stock updater.[1][7]
/usr/local/cpanel/scripts/upcp --force
/usr/local/cpanel/cpanel -V
WHM: Home → cPanel → Upgrade to Latest Version → Click to Upgrade. Confirm the printed version is ≥ the floor, not merely that upcp exited 0.
- If
upcpcannot run today, install WP Toolkit 6.11.8. That is the only mitigation on the current article (updated 19 Nov). Command from the article, prompt and all:[1]
bash <(curl https://wp-toolkit.plesk.com/cPanel/installer.sh || wget -O - https://wp-toolkit.plesk.com/cPanel/installer.sh) --version 6.11.8
Read that script before you pipe it. It is root. After it returns, check the package - previous WP Toolkit advisories used wp-toolkit-cpanel:
rpm -q wp-toolkit-cpanel
# Ubuntu:
dpkg -l wp-toolkit-cpanel
Want 6.11.8 or newer. We did not run the installer. The article does not publish a NEVRA. A HEAD of installer.sh this morning returned HTTP/2 200, last-modified: Thu, 19 Nov 2026 16:47:38 GMT - same calendar day as the article update. That is existence, not a signature check.
-
Do not treat 6.11.8 as a substitute for the cPanel floor. Vendor order is: upgrade cPanel; Toolkit 6.11.8 only if you cannot yet.[1]
-
Do not use third-party
wptk.proxypassLeika one-liners as the official workaround. They are not on the current vendor article. The published interim is 6.11.8.[1] -
Shared and reseller boxes first. Unauthenticated, network-reachable panel bugs are what scanners queue. Single-owner VPS still patch; the impact sentence is still server control.[1]
Versions with no floor
"All Supported Versions" means every train WebPros still ships. If you are on a major that is already EOL, there is no 110.0.159 / 134.0.72 / 136.0.52 / 138.0.25 for you. Move the server onto a supported major, or replace the panel. Staying on an abandoned train is not a mitigation.[1]
LTS 110: you stay on 110; you still need 110.0.159+. Pinning CURRENT away does not skip the TSR on 110.[5][6]
Compromise signs
None of these prove this bulletin by themselves. Together they are enough to snapshot, rotate, and restore from known-good.
/usr/local/cpanel/cpanel -Vbelow the floor and 2082/2083/2086/2087 reachable from the internet during 18-20 Nov.- New root or
wp-toolkitcron, new keys under/root/.ssh/, new PHP under/usr/local/cpanel/3rdparty/wp-toolkit/dated after 18 Nov that you did not deploy. - New WordPress administrators you did not create, on multiple accounts, same window - that is not a unique IoC; it is "look anyway."
- WP Toolkit still reporting < 6.11.8 after you thought the installer ran.
The vendor published no log signature. Do not grep for a path we invented.
FAQ
Is there a CVE? Not on the vendor article, not in our NVD keyword pull, not in KEV. Track 45133380394135. When WebPros publishes an ID, map it to this floor - do not assume it is 87900 / 93699 / 105476.[1][8][9]
Does WordPress 7.1.4 cover this? No. That patched CVE-2026-119977 in core. This is cPanel.
Does Auto-Update mean I am fine? Only if the box actually landed ≥ the floor. Check cpanel -V. License-expired or version-pinned servers skip upcp and sit.[7]
Can I just disable WP Toolkit? The vendor did not list that as a mitigation. They listed 6.11.8 and the cPanel builds.[1]
What we are not claiming
- We did not exploit this. No request was sent.
- We did not reconstruct a payload or name a proxy URL.
- No CVE, CVSS, CWE, finder, or in-the-wild statement from the vendor.[1]
- Not on CISA KEV catalog 2026.11.18 / 1,786.[8]
- NVD November keyword search: 0 rows.[9]
- We did not run
upcpor the Plesk CDN installer on a lab box. - Third-party posts that add a Leika override, a finder name, or "exposed even with no WordPress sites" are not sources we used for those extra claims.
- 138.0.27 / 138.0.28 (19 Nov TSR) are not this article. Floor for this bug is still 138.0.25+.[2]
Sources
[1] https://support.cpanel.net/hc/en-us/articles/45133380394135-Security-Vulnerability-in-cPanel-WHM-s-WP-Toolkit-Proxy-November-18-2026 - cPanel WP Toolkit Proxy advisory Nov 18 2026 [2] https://docs.cpanel.net/changelogs/138-change-log - cPanel 138 change log [3] https://docs.cpanel.net/changelogs/136-change-log - cPanel 136 change log [4] https://docs.cpanel.net/changelogs/134-change-log - cPanel 134 change log [5] https://docs.cpanel.net/changelogs/110-change-log - cPanel 110 change log [6] https://docs.cpanel.net/release-notes/release-notes - cPanel release notes [7] https://support.cpanel.net/hc/en-us/articles/1500004959421-How-do-I-update-cPanel-WHM - How do I update cPanel/WHM [8] https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json - CISA KEV catalog JSON [9] https://services.nvd.nist.gov/rest/json/cves/2.0?keywordSearch=cPanel%20WP%20Toolkit&pubStartDate=2026-11-01T00:00:00.000&pubEndDate=2026-11-20T23:59:59.000 - NVD keyword search cPanel WP Toolkit Nov 2026