LiteSpeed User-End cPanel Plugin before 2.4.5 allows privilege escalation (possibly to root), as exploited in the wild in May 2026. Detection is best done via a command line of grep -rE "cpanel_jsonapi_func=redisAble" /var/cpanel/logs /usr/local/cpanel/logs/ 2>/dev/null in Bash. If you get no output, you have not been hit with exploitation of the vulnerability. If there is output, we recommend you examine the IP addresses in the list, determine if they are valid IP addresses, and if not, block them. To determine damage done, examine the system logs for use by the detected IP addresses. The issue is related to mishandling of Redis enable/disable features. The recommended minimum version is 2.4.7.
CVE-2026-48172
“—” beside the score: it is equal to NVD's CVSS score.
Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-05-26), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low mission impact
Installation of LiteSpeed WHM PlugIn 5.3.1.0 and cPanel 2.4.7 (from the CVE record's solution, MITRE Corporation) — apply it.
- CVSS v3
- 9.8
- EG Score
- 9.8CRITICALhigh confidence
- EG Risk
- 99EG Risk 99/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity98% × 45%The EG Score, 9.8 of 10.Exploitation100% × 40%Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Attend at low mission impact; Act at medium or high.Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: Installation of LiteSpeed WHM PlugIn 5.3.1.0 and cPanel 2.4.7 (from the CVE record's solution, MITRE Corporation). Apply it sooner than your standard update timelines at low mission impact and as soon as possible at medium or high. - EPSS PROB
- 1.0%
- EPSS %ILE
- 62nd
- KEV
- ⚠ Exploited
SSVC (CISA's decision table, applied by EchelonGraph)Attend at low mission impact; Act at medium or high.
Installation of LiteSpeed WHM PlugIn 5.3.1.0 and cPanel 2.4.7 (from the CVE record's solution, MITRE Corporation). Apply it sooner than your standard update timelines at low mission impact and as soon as possible at medium or high.
Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.
In CISA KEV yes (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
CISA required action“Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.”
Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://blog.litespeedtech.com/2026/05/21/security-update-for-litespeed-cpanel-plugin/ · https://nvd.nist.gov/vuln/detail/CVE-2026-48172
Published
May 21, 2026
Last Modified
October 7, 2026
Advisory Details (4)
Auto-updated Oct 7, 2026Known Exploited Vulnerabilities Catalog | CISA
Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-48172Control Panel Plugins Release Log - LiteSpeed Technologies
https://www.litespeedtech.com/products/litespeed-web-server/control-panel-support/release-logcPanel Plugin Features - LiteSpeed Technologies
https://www.litespeedtech.com/products/litespeed-web-server/control-panel-support/cpanelSecurity Update for LiteSpeed cPanel Plugin ⋆ LiteSpeed Blog
https://blog.litespeedtech.com/2026/05/21/security-update-for-litespeed-cpanel-plugin/Vendor Advisories for CVE-2026-48172(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 60× in last 7d / 254× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 100 of 1,126 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 1,026 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
- 2026-10-12 14:49 UTCEG score recompute
- 2026-10-12 14:49 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-12 08:43 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-12 04:53 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-12 01:08 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-11 21:21 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-11 19:44 UTCEG score recompute
- 2026-10-11 17:33 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-11 16:58 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
- 2026-10-11 13:45 UTCEG score recompute
- 2026-10-11 13:45 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-11 09:59 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-11 06:13 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-11 02:27 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-10 22:39 UTCEG score recompute
- 2026-10-10 22:39 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
- 2026-10-10 18:53 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-10 15:06 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-10 11:20 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-10 07:34 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-10 03:48 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-10 00:02 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
Show 75 moreShow fewer
- 2026-10-09 20:17 UTCEG score recompute
- 2026-10-09 20:16 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
- 2026-10-09 16:30 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-09 12:44 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-09 08:58 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-09 05:13 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-09 01:27 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-08 21:41 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-08 17:55 UTCEG score recompute
- 2026-10-08 17:55 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-08 17:12 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
- 2026-10-08 14:09 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-08 10:21 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-08 06:35 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-08 02:50 UTCEG score recompute
- 2026-10-08 02:50 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
- 2026-10-07 23:04 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-07 19:19 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-07 18:27 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-07 16:14 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-07 12:28 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-07 08:43 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-07 04:57 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-07 01:11 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-06 21:25 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-06 17:39 UTCEG score recompute
- 2026-10-06 17:39 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-10-06 13:54 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-06 10:08 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-06 06:22 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-06 02:37 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-05 22:51 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-05 19:06 UTCEG score recompute
- 2026-10-05 19:06 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-10-05 15:21 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-05 11:35 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-05 07:50 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-05 04:04 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-05 00:17 UTCEG score recompute
- 2026-10-05 00:16 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-10-04 20:29 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-04 16:43 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-04 12:57 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-04 09:11 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-04 05:26 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-04 01:41 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-03 21:55 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-03 18:08 UTCEG score recompute
- 2026-10-03 18:07 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-03 14:25 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-10-03 14:19 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-03 10:33 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-03 06:47 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-03 03:01 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-02 23:15 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-02 19:28 UTCEG score recompute
- 2026-10-02 19:28 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-02 15:43 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-02 11:57 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-02 08:08 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-02 04:22 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-02 00:37 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-01 20:52 UTCEG score recompute
- 2026-10-01 20:51 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-10-01 17:03 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-01 13:17 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-01 09:32 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-01 05:46 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-01 02:00 UTCGHSA enrichmentGHSA-fxrh-cwjh-m33v · GitHub severity CRITICAL · GitHub CVSS 9.8
Publicly available exploits
(1 reference)Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.
- GitHub PoCHORKimhab/CVE-2026-48172Published May 23, 2026
CVE-2026-48172
Open source ↗
Related CVEs(same CWE)
Frequently asked(6)
What is CVE-2026-48172?
When was the CVE record for CVE-2026-48172 published?
Is CVE-2026-48172 actively exploited?
What is the CVSS score of CVE-2026-48172?
Which products are affected by CVE-2026-48172?
How do I remediate CVE-2026-48172?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-48172
Is Your Infrastructure Affected by CVE-2026-48172?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.