dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 18 Jun 2026.
Litespeed Cpanel PluginPlugin / extension · Litespeedtech

CVE-2026-54420

HIGH · 8.5 CVSS v3.1 Published 2026-06-14
Fix available
A fix is available. Upgrade to 2.4.8 / 5.3.2.0 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
LiteSpeed cPanel plugin before 2.4.8 (as distributed in LiteSpeed WHM PlugIn before 5.3.2.0) mishandles symlinks provided by a user with FTP or web shell access on a shared hosting server running CloudLinux/CageFS, as exploited in the wild in May 2026.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

LiteSpeed cPanel plugin before 2.4.8 (and WHM PlugIn before 5.3.2.0) improperly handles symlinks created by users with FTP or web shell access on shared hosting servers running CloudLinux/CageFS. This allows authenticated users to potentially access files outside their allocated cage or escalate privileges by creating malicious symlinks.

MitigationUpgrade LiteSpeed cPanel plugin to version 2.4.8 or later, and WHM PlugIn to 5.3.2.0 or later. Since this vulnerability was exploited in the wild, immediate patching is critical.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Litespeed Cpanel PluginPlugin / extension
Affected:< 2.4.8
Litespeed Whm PluginPlugin / extension
Affected:< 5.3.2.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check LiteSpeed cPanel Plugin version
    Locate the installed LiteSpeed cPanel plugin version. This is typically found in the cPanel plugin management area or via command line tools that query the plugin metadata.
    Affected if The installed version is lower than 2.4.8
  2. Check LiteSpeed WHM Plugin version
    Locate the installed LiteSpeed WHM plugin version. This is typically found in the WHM plugin management area or via command line tools that query the plugin metadata.
    Affected if The installed version is lower than 5.3.2.0
  3. Verify CloudLinux/CageFS is enabled
    Check whether CloudLinux with CageFS is active on the shared hosting server. This is a required condition for the vulnerability to be exploitable.
    Affected if CloudLinux and CageFS are both enabled on the server
  4. Inspect user-created symlinks in shared directories
    Examine the /home directory and other shared hosting directories for symlinks created by user accounts. Look for symlinks that point outside the user's designated directory or to sensitive system files.
    Affected if Symlinks created by non-privileged users exist in the shared hosting environment and point to files outside the user's isolation boundary

A server is affected if it runs a LiteSpeed cPanel plugin version below 2.4.8 or WHM plugin version below 5.3.2.0, has CloudLinux/CageFS enabled, and contains user-created symlinks that could be used to escape isolation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.4.8 / 5.3.2.0 or later
Fixed in 2.4.85.3.2.0
Interim mitigation

Upgrade LiteSpeed cPanel plugin to version 2.4.8 or later, and WHM PlugIn to 5.3.2.0 or later. Since this vulnerability was exploited in the wild, immediate patching is critical.

Recommended fix High confidence

LiteSpeed cPanel Plugin 2.4.8+ or LiteSpeed WHM Plugin 5.3.2.0+

  1. Identify the currently installed LiteSpeed cPanel Plugin version by checking the plugin interface or running: rpm -q lsws
  2. Identify the currently installed LiteSpeed WHM Plugin version by checking: rpm -q lsws-whm-plugin
  3. If running LiteSpeed cPanel Plugin version is less than 2.4.8, upgrade to version 2.4.8 or later
  4. If running LiteSpeed WHM Plugin version is less than 5.3.2.0, upgrade to version 5.3.2.0 or later
  5. Download the latest LiteSpeed plugins from the official LiteSpeed repository or LiteSpeed customer portal
  6. Install the updated plugin packages using the appropriate package manager (rpm or via WHM/CPanel interface)
  7. Restart LiteSpeed services after upgrade to ensure changes take effect
  8. Verify the installed version matches or exceeds the fixed releases
Caveat Review release notes for any configuration changes or required updates to existing setups

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Litespeed Cpanel Plugin Exploited in the wild — priority engagement
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54420 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-54420 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data