A practical response checklist for exposed cPanel and WHM hosts
The testmetest incident gives hosting teams a specific reason to review cPanel and WHM exposure. JFrog found shellpanel workflows in a hijacked GitHub owner cluster that were connected to earlier Socket reporting on cPanel scanning through CVE-2026-41940. The connection is operational and does not confirm a downstream compromise.
This checklist is for teams that need to validate their own systems without turning a global product count into a victim claim.
1. Confirm the scope
List owned cPanel and WHM hosts from DNS, cloud accounts, hosting contracts, and configuration management. Add externally observed candidates from approved ZoomEye results. The stored app="cPanel" query returned 10,122,751 global product observations on November 19, 2026. The result is a global baseline and must be matched to owned address ranges and domains.
Record the exact dork, time, scope, owner, and matching method. Do not count the global total as affected systems.
2. Validate public exposure
Confirm whether the panel is reachable from the internet. Review firewall rules, load balancers, CDN behavior, DNS, and hosting-provider controls. Disable public access where the business requirement does not justify it.
If the service must remain public, restrict source networks where possible, enforce strong authentication, and review the administrative accounts and integrations.
3. Check the installed build
cPanel states that CVE-2026-41940 affected every cPanel and WHM version after v11.40 and WP Squared through v11.136.1.6. Fixes were released on April 28, 2026, with later updates for selected legacy versions.
Use host configuration or approved administrative access to confirm the installed build. Record the update time and any temporary mitigation. Do not infer patch state from a public product fingerprint.
4. Review session and access evidence
Inspect session files, authentication logs, Basic authentication paths, command history, file changes, and access to configuration secrets. Use the current cPanel detection script and preserve logs before cleanup. The vendor revised the script after partner testing found a false positive on session lock files.
If you find unexpected access, move into the formal incident process. Preserve the evidence, identify the actor path, and coordinate containment with the hosting and application owners.
5. Rotate exposed credentials
The cPanel link sits inside a broader npm and GitHub compromise. Credentials stored on a hosting server may include repository tokens, deployment keys, database passwords, API keys, or customer secrets. Review what was available to each affected process and rotate material that could have been exposed.
Do not revoke every credential at once without checking the destructive behavior reported in the npm campaign. The Register reported a wiper that could trigger after a stolen GitHub token was revoked. Coordinate revocation with backups, logging, and the owner of each dependent service.
6. Trace release and repository links
Review repositories and workflows that can publish packages or deploy to the hosting environment. Check branch protection, workflow permissions, deploy keys, and recent publication records. A clean cPanel patch check does not close the supply-chain question if the release identity remains compromised.
7. Document the result
For each host record external visibility, confirmed build, log outcome, credential review, patch status, and owner. Use remediated, validated, unresolved, or not owned rather than broad labels such as compromised without evidence.
8. Schedule the follow-up
Run a stable external observation cadence and compare results with the host register. Recheck patch state after maintenance and alert on new administrative exposure. Continue monitoring identity, runner, and package activity for the affected release path.
The checklist ends only when the evidence supports a conclusion for each owned system. It should not end because a global count is large, a change query returns zero, or a public panel appears patched.
Top comments (0)