CVE-2026-62988

CRITICALPre-NVD 9.09.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-18. A secondary CVSS source baseline 9.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-61216 (ENISA EUVD) · GHSA-7788-ghfq-c6mh (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Froxlor is open source server administration software. From 2.3.7 until 2.3.8, the Customers.get, Customers.listing, Admins.get, Admins.listing, Ftps.get, and Ftps.listing API commands in lib/Froxlor/Api/Commands/Customers.php, lib/Froxlor/Api/Commands/Admins.php, and lib/Froxlor/Api/Commands/Ftps.php retrieve full database rows and return them without removing password and data_2fa fields. An authenticated API caller with permission to use these endpoints can obtain customer, administrator, and FTP password hashes as well as Base32-encoded TOTP seeds for administrator and customer accounts. Password hashes can be cracked offline, and TOTP seeds can generate valid second-factor codes until two-factor authentication is reset. Exposure of both values for an account can enable takeover of the hosting panel or hosted resources and can defeat both authentication factors. This issue is fixed in version 2.3.8.

CVSS v3
9.0
EG Score
9.0CRITICALmedium confidence
EG Risk
57
EG Risk 57/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity90% × 45%
Impact severity (EG Severity): CVSS 9.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
50th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is its impact severity (EG Severity), not escalated.

EG Severity
9.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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

Published

August 18, 2026

Last Modified

September 8, 2026

Advisory Details (4)

Auto-updated Aug 18, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub release Patch Available

froxlor security release 2.3.8

Patch available: froxlor/froxlor 2.3.8

https://github.com/froxlor/froxlor/releases/tag/2.3.8
GitHub commit Patch Available

commit 8667fa3a4d77 (froxlor/froxlor)

Patch available: froxlor/froxlor 2.3.8 (contains commit 8667fa3a4d77)

https://github.com/froxlor/froxlor/commit/8667fa3a4d77d6e322b7b8f7b9edbc1613ab5797
GitHub commit Patch Available

commit 52a43fb826bb (froxlor/froxlor)

Patch available: froxlor/froxlor 2.3.8 (contains commit 52a43fb826bb)

https://github.com/froxlor/froxlor/commit/52a43fb826bb9a058faf9c39feeef7ac4444ceba
GitHub advisoryMentions a patch (unverified)

Credential and 2FA secret disclosure via Froxlor API endpoints · Advisory · froxlor/froxlor · GitHub

https://github.com/froxlor/froxlor/security/advisories/GHSA-7788-ghfq-c6mh

Vendor Advisories for CVE-2026-62988(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
composerfroxlor/froxlor @ 2.3.8 (fixes < 2.3.8)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
froxlor/froxlor0.10.0 ... 2.3.7 (109 versions)
  • every version up to 2.3.8: fixed in 2.3.8
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 61× 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 140 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 40 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  2. 2026-11-01 11:12 UTCGHSA enrichmentGHSA-7788-ghfq-c6mh · GitHub severity CRITICAL · GitHub CVSS 9.0
  3. 2026-11-01 07:41 UTCGHSA enrichmentGHSA-7788-ghfq-c6mh · GitHub severity CRITICAL · GitHub CVSS 9.0
  4. 2026-11-01 07:41 UTCEG score recompute
  5. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  6. 2026-10-31 10:21 UTCEG score recompute
  7. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  8. 2026-10-30 09:26 UTCEG score recompute
  9. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  10. 2026-10-29 08:35 UTCEG score recompute
  11. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  12. 2026-10-28 07:39 UTCEG score recompute
  13. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  14. 2026-10-27 06:48 UTCEG score recompute
  15. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  16. 2026-10-26 02:33 UTCEG score recompute
  17. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  18. 2026-10-25 14:13 UTCEG score recompute
  19. 2026-10-25 01:42 UTCEG score recompute
  20. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  21. 2026-10-24 00:50 UTCEG score recompute
  22. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  23. 2026-10-22 23:59 UTCEG score recompute
  24. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  25. 2026-10-21 23:05 UTCEG score recompute
Show 75 more
  1. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  2. 2026-10-20 22:10 UTCEG score recompute
  3. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  4. 2026-10-19 21:16 UTCEG score recompute
  5. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  6. 2026-10-18 20:12 UTCEG score recompute
  7. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  8. 2026-10-18 03:23 UTCEG score recompute
  9. 2026-10-17 19:20 UTCEG score recompute
  10. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  11. 2026-10-16 18:27 UTCEG score recompute
  12. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  13. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  14. 2026-10-15 15:08 UTCEG score recompute
  15. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  16. 2026-10-14 09:32 UTCEG score recompute
  17. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  18. 2026-10-13 07:08 UTCEG score recompute
  19. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  20. 2026-10-12 15:49 UTCEG score recompute
  21. 2026-10-11 19:33 UTCEG score recompute
  22. 2026-10-11 16:48 UTCEG score recompute
  23. 2026-10-11 14:10 UTCEG score recompute
  24. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  25. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  26. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  27. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  28. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  29. 2026-10-06 17:06 UTCEG score recompute
  30. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  31. 2026-10-06 08:21 UTCEG score recompute
  32. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  33. 2026-10-05 01:53 UTCEG score recompute
  34. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  35. 2026-10-03 17:37 UTCEG score recompute
  36. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  37. 2026-10-02 18:55 UTCEG score recompute
  38. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  39. 2026-10-02 01:25 UTCEG score recompute
  40. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  41. 2026-09-30 20:49 UTCEG score recompute
  42. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  43. 2026-09-30 09:47 UTCEG score recompute
  44. 2026-09-28 21:55 UTCEG score recompute
  45. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  46. 2026-09-27 16:18 UTCEG score recompute
  47. 2026-09-27 07:54 UTCEG score recompute
  48. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  49. 2026-09-24 16:04 UTCEG score recompute
  50. 2026-09-23 20:19 UTCEG score recompute
  51. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  52. 2026-09-22 20:24 UTCEG score recompute
  53. 2026-09-21 22:03 UTCEG score recompute
  54. 2026-09-20 22:21 UTCEG score recompute
  55. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  56. 2026-09-19 18:42 UTCEG score recompute
  57. 2026-09-18 21:50 UTCEG score recompute
  58. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  59. 2026-09-17 21:45 UTCEG score recompute
  60. 2026-09-16 15:58 UTCEG score recompute
  61. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  62. 2026-09-16 07:38 UTCEG score recompute
  63. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  64. 2026-09-15 03:54 UTCEG score recompute
  65. 2026-09-13 19:06 UTCEG score recompute
  66. 2026-09-12 16:28 UTCEG score recompute
  67. 2026-09-11 17:37 UTCEG score recompute
  68. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  69. 2026-09-11 13:13 UTCEG score recompute
  70. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  71. 2026-09-10 12:31 UTCEG score recompute
  72. 2026-09-09 03:23 UTCEG score recompute
  73. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  74. 2026-09-07 16:07 UTCEG score recompute
  75. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.6% · 45th percentile

Frequently asked(5)

What is CVE-2026-62988?
CVE-2026-62988 is a critical-severity vulnerability; its CVE record was published on August 18, 2026. Froxlor is open source server administration software. From 2.3.7 until 2.3.8, the Customers.get, Customers.listing, Admins.get, Admins.listing, Ftps.get, and Ftps.listing API commands in lib/Froxlor/Api/Commands/Customers.php, lib/Froxlor/Api/Commands/Admins.php, and…
When was the CVE record for CVE-2026-62988 published?
The CVE record for CVE-2026-62988 was published on August 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 8, 2026; the record at its source may have been updated since.
Is CVE-2026-62988 actively exploited?
CVE-2026-62988 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62988?
CVE-2026-62988 has a CVSS base score of 9.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-62988?
A fix for CVE-2026-62988 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-62988 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-62988

Explore →

Is Your Infrastructure Affected by CVE-2026-62988?

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