Skip to content
major vulnerability· requires attention

Widely deployed hosting/control panel plugin; critical privilege escalation with root access; observed in the wild; affects many environments.

Applications

CVE-2026-48172

10.0
Critical
KEV · Exploited in wildEPSS 19%Patch availableMay 21, 2026

Privilege escalation in LiteSpeed User-End cPanel Plugin <2.4.5; active in the wild.

common questions

Is CVE-2026-48172 being exploited?

Yes. CVE-2026-48172 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2026-48172?

CVE-2026-48172 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-48172?

Yes. A fix has been recorded for CVE-2026-48172. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-48172 affect?

CVE-2026-48172 affects LiteSpeed User-End cPanel Plugin < 2.4.5, LiteSpeed cPanel integration. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-48172?

Upgrade to 2.4.5+; monitor logs for indicators.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
LiteSpeed User-End cPanel Plugin < 2.4.5LiteSpeed cPanel integration
impact

Local privilege escalation to root via mis-handled Redis enable/disable in the plugin.

action required

Immediate action required

affected versions
LiteSpeed Technologies cPanel Plugin
  • affected>= 2.3 and < 2.4.7
LiteSpeed Technologies WHM Plugin
  • affected< 5.3.1.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free