cPanel has fixed 11 remote code execution flaws across three advisories covering WHM SSL handling, the WP Toolkit proxy and the ea-nginx package. Rapid7 notes a public proof of concept for one of the NGINX bugs, and no live attacks are known.
Three Advisories Cover Reseller, Unauthenticated and NGINX Attack Paths
The first advisory covers an SSL handling bug that lets a reseller with SSL rights run code as root. The second involves the WP Toolkit Proxy, where an unauthenticated remote attacker can run code and take over the host. The third, EasyApache4 version 25.98, patches nine NGINX bugs in ea-nginx led by CVE-2026-123007 and CVE-2026-123633, which are HTTP/2 memory flaws.
Together the three advisories account for the 11 flaws: the two SSL and WP Toolkit issues plus nine in ea-nginx.
Public PoC for CVE-2026-123007 Noted by Rapid7
Rapid7 notes that a public proof of concept exists for CVE-2026-123007. No live attacks are known for any of the flaws. A published exploit for a memory flaw in a widely deployed web server module shortens the time between disclosure and potential attack.
Root Takeover of Shared Hosting Servers
The impact is root takeover of shared hosting servers. The WP Toolkit Proxy flaw is the most direct of the paths because it needs no authentication, while the SSL bug requires a reseller account with SSL rights, a privilege that hosting providers routinely hand to customers.
Why cPanel’s Market Share Raises the Stakes
cPanel holds roughly 22 to 23 percent of tracked hosting panels, according to the reporting, which gives the advisories reach across a large share of hosting providers. A single flaw in the panel or its bundled web server components can expose many customer sites at once on a shared server.
Fixed Versions for cPanel & WHM, ea-nginx and WP Toolkit
cPanel & WHM should be updated to 11.138.0.2, 11.136.0.54, 11.134.0.77 or 11.110.0.164, depending on the release line in use. The ea-nginx package should be updated to 1.31.9, and WP Toolkit to 6.11.8.
Interim Measures Without Immediate Patching
For servers that cannot update immediately, the guidance lists two interim steps: remove reseller SSL rights, which closes the SSL path, and remove the ea-nginx-http2 module, which addresses the HTTP/2 memory flaws. Neither step substitutes for the updates, but they cut off two of the attack paths in the interim.
Patch Timing Against a Published Exploit
The advisories arrived in a two-day span, and the existence of a public proof of concept for CVE-2026-123007 means attackers have a starting point for exploitation attempts against unpatched servers. Hosting providers face a practical sequencing question across four supported cPanel release lines, each with its own fixed version, which complicates fleet-wide patching.
Differences in Exploitation Requirements Across the Three Advisories
The advisories carry different prerequisites. The WP Toolkit Proxy bug requires no authentication, the SSL bug requires a reseller account holding SSL rights, and the ea-nginx HTTP/2 memory flaws, led by CVE-2026-123007 and CVE-2026-123633, are reached through network requests to the web server module. The interim measures reflect that split: removing reseller SSL rights closes the SSL path, while removing the ea-nginx-http2 module addresses the HTTP/2 flaws. No interim measure is described for the WP Toolkit Proxy flaw, which makes the WP Toolkit 6.11.8 update the sole listed fix for the unauthenticated path. Rapid7’s note about the public proof of concept applies specifically to CVE-2026-123007.
The four fixed cPanel & WHM versions, 11.138.0.2, 11.136.0.54, 11.134.0.77 and 11.110.0.164, show that cPanel maintains several release lines in parallel. A hosting provider running more than one line has to track the correct fixed version for each, alongside the separate ea-nginx 1.31.9 and WP Toolkit 6.11.8 updates, to cover all three advisories.
