CVE-2026-84761

HIGHPre-NVD 7.27.2—
EchelonGraph scoreHIGH confidence

Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2026-09-03. a secondary CVSS source baseline 7.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.2Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Unauthenticated Server Side Request Forgery (SSRF) in LiteSpeed Cache <= 7.9 versions.

CVSS v3
7.2
EG Score
7.2(high)
EG Risk
47(Track)
EG Risk 47/100SSVC: Track

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
Severity72% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

September 3, 2026

Last Modified

September 4, 2026

Advisory Details (1)

Auto-updated Sep 3, 2026
No patch confirmed yet.
generic

Server Side Request Forgery (SSRF) in WordPress LiteSpeed Cache Plugin - Patchstack

https://patchstack.com/database/wordpress/plugin/litespeed-cache/vulnerability/wordpress-litespeed-cache-plugin-7-9-server-side-request-forgery-ssrf-vulnerability?_s_id=cve

Vendor Advisories for CVE-2026-84761(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 29× in last 7d / 69× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-21 02:07 UTCEG score recompute
  2. 2026-09-21 02:07 UTCGHSA enrichment
  3. 2026-09-20 20:16 UTCEPSS rescore
  4. 2026-09-20 15:02 UTCGHSA enrichment
  5. 2026-09-20 03:58 UTCGHSA enrichment
  6. 2026-09-19 16:53 UTCEG score recompute
  7. 2026-09-19 16:53 UTCGHSA enrichment
  8. 2026-09-19 05:49 UTCEG score recompute
  9. 2026-09-19 05:48 UTCGHSA enrichment
  10. 2026-09-18 19:28 UTCEPSS rescore
  11. 2026-09-18 18:43 UTCGHSA enrichment
  12. 2026-09-18 07:39 UTCGHSA enrichment
  13. 2026-09-17 20:35 UTCEG score recompute
  14. 2026-09-17 20:35 UTCGHSA enrichment
  15. 2026-09-17 19:32 UTCEPSS rescore
  16. 2026-09-17 09:01 UTCGHSA enrichment
  17. 2026-09-16 21:57 UTCEG score recompute
  18. 2026-09-16 21:57 UTCGHSA enrichment
  19. 2026-09-16 14:09 UTCEPSS rescore
  20. 2026-09-16 10:53 UTCEG score recompute
  21. 2026-09-16 10:53 UTCGHSA enrichment
  22. 2026-09-16 05:15 UTCEPSS rescore
  23. 2026-09-15 23:49 UTCGHSA enrichment
  24. 2026-09-15 12:43 UTCEG score recompute
  25. 2026-09-15 12:43 UTCGHSA enrichment
Show 44 more
  1. 2026-09-15 03:12 UTCEPSS rescore
  2. 2026-09-15 03:12 UTCEPSS rescore
  3. 2026-09-15 01:39 UTCGHSA enrichment
  4. 2026-09-14 14:35 UTCGHSA enrichment
  5. 2026-09-14 03:31 UTCEG score recompute
  6. 2026-09-14 03:31 UTCGHSA enrichment
  7. 2026-09-13 16:27 UTCGHSA enrichment
  8. 2026-09-13 05:23 UTCGHSA enrichment
  9. 2026-09-12 18:19 UTCEG score recompute
  10. 2026-09-12 18:19 UTCGHSA enrichment
  11. 2026-09-12 07:15 UTCGHSA enrichment
  12. 2026-09-11 20:10 UTCEG score recompute
  13. 2026-09-11 20:10 UTCGHSA enrichment
  14. 2026-09-11 08:41 UTCGHSA enrichment
  15. 2026-09-10 21:37 UTCGHSA enrichment
  16. 2026-09-10 10:33 UTCEG score recompute
  17. 2026-09-10 10:32 UTCGHSA enrichment
  18. 2026-09-09 23:27 UTCGHSA enrichment
  19. 2026-09-09 10:11 UTCGHSA enrichment
  20. 2026-09-08 23:07 UTCEG score recompute
  21. 2026-09-08 23:07 UTCGHSA enrichment
  22. 2026-09-08 22:01 UTCEPSS rescore
  23. 2026-09-08 06:59 UTCGHSA enrichment
  24. 2026-09-07 19:55 UTCEG score recompute
  25. 2026-09-07 19:55 UTCGHSA enrichment
  26. 2026-09-07 08:50 UTCGHSA enrichment
  27. 2026-09-06 21:44 UTCEG score recompute
  28. 2026-09-06 21:44 UTCGHSA enrichment
  29. 2026-09-06 13:48 UTCEPSS rescore
  30. 2026-09-06 10:39 UTCGHSA enrichment
  31. 2026-09-05 23:35 UTCEG score recompute
  32. 2026-09-05 23:35 UTCGHSA enrichment
  33. 2026-09-05 15:31 UTCEPSS rescore
  34. 2026-09-05 12:31 UTCGHSA enrichment
  35. 2026-09-05 01:25 UTCGHSA enrichment
  36. 2026-09-04 14:21 UTCEG score recompute
  37. 2026-09-04 14:21 UTCGHSA enrichment
  38. 2026-09-04 13:54 UTCEG score recompute
  39. 2026-09-04 13:54 UTCGHSA enrichment
  40. 2026-09-04 04:43 UTCEG score recompute
  41. 2026-09-04 04:42 UTCGHSA enrichment
  42. 2026-09-03 17:36 UTCEG score recompute
  43. 2026-09-03 16:34 UTCEG score recompute
  44. 2026-09-03 16:33 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-84761?
CVE-2026-84761 is a high vulnerability published on September 3, 2026. Unauthenticated Server Side Request Forgery (SSRF) in LiteSpeed Cache <= 7.9 versions.
When was CVE-2026-84761 disclosed?
CVE-2026-84761 was first published in the National Vulnerability Database on September 3, 2026, with the most recent update on September 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-84761 actively exploited?
CVE-2026-84761 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.5% of all scored CVEs.
What is the CVSS score of CVE-2026-84761?
CVE-2026-84761 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-84761?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-84761, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-84761

Explore →

Is Your Infrastructure Affected by CVE-2026-84761?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs