Skip to main content
Published on August 12, 2026
CVE-2026-54420, CVSS 8.5. Affects the LiteSpeed cPanel plugin before 2.4.8, shipped in the LiteSpeed WHM plugin before 5.3.2.0. Fixed in WHM plugin 5.3.2.1 or later. Added to CISA’s Known Exploited Vulnerabilities catalog on 15 June 2026.

Why this one is different

Most advisories we publish concern software you run yourself. This one concerns the machine underneath a shared hosting account — and it inverts the trust model that shared hosting is sold on. The premise of shared hosting is that accounts are neighbours who cannot reach each other. CloudLinux and CageFS exist to enforce exactly that. This flaw lets one neighbour with nothing more than an FTP account walk out of their box and become root on the host. At that point every site on the server is readable, writable, and modifiable by someone who paid for the cheapest plan on it.

The flaw

The plugin mishandles symbolic links. An account with FTP or web shell access can plant a symlink that the plugin follows while running with elevated rights, and use that to escalate to root. No exploit of a memory bug, no race against a kernel. Just a privileged process trusting a path that an unprivileged user controls — the oldest shape of local privilege escalation there is, and still one of the most effective. Two properties make it serious rather than merely interesting: The entry bar is low. FTP access is the least-privileged thing a shared host hands out. It is what every customer gets, including the one who bought a plan with a stolen card an hour ago. It is confirmed exploited. CISA does not add flaws to KEV on theory. The catalog entry, dated 15 June 2026, means it has been used against real systems. The issue was reported by Namecheap on 31 May 2026 — a hosting provider finding it in its own fleet, which tells you something about where it shows up.

Sizing your exposure

Worth separating two things that share a name. This is a flaw in the cPanel plugin distributed by LiteSpeed, not in LiteSpeed Web Server itself. If you run LSWS on a VPS you manage alone, without cPanel, you are not in scope.

Checking and updating

Check the installed plugin version from WHM, or on the command line:
Update through WHM, or from the shell:
Then confirm you are on 5.3.2.1 or later before considering it closed.

Looking for signs it was used

Patching stops it happening again; it says nothing about the past. Because exploitation is confirmed in the wild, a server that ran a vulnerable version deserves a look. The tell is a burst of plugin calls in quick succession — the exploit needs several concurrent attempts to win. In the plugin’s logs, look for generateEcCert immediately followed by packageUserSize, and for clusters of roughly seven to ten concurrent calls per attempt:
Alongside that, the usual root-compromise checks: accounts added recently, SSH keys you did not install, and scheduled jobs nobody remembers writing.
If any of that turns up something you cannot account for, treat the host as compromised. On a shared server that means every account on it, not just the one that was used as the way in — rebuild, restore customer data from backups predating the first suspicious event, and rotate every credential the machine held.

What it says about shared hosting

Nothing here argues against shared hosting. It argues for being clear about what it is: a machine where the isolation between accounts is a software product, and software products have bugs. If your workload genuinely cannot tolerate a hostile neighbour, the answer is not a better plugin — it is not sharing the kernel. That is the actual line between shared hosting and a VPS, and it is worth choosing deliberately rather than on price. Questions about your hosting with us? Our team is available from your client area.