Skip to main content
VulnerabilityPublished Updated

CVE-2026-62988: froxlor · Information Exposure

Affects froxlorSource GCVE Database

0
Compare

Not known to be exploited · CVSS 9.0 Critical : upgrade to 2.3.8 as a priority.

Data as of 9 Nov 2026, 23:24 UTC

CVSS 3.1 base score
9.0Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.19.0
EPSS
0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.3.8
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Upgrade froxlor/froxlor to 2.3.8.

Affected software

ProductAffectedFixed in
GitHubfroxlor/froxlorpkg:github/froxlor/froxlorOther threatsAffected
  • <2.3.8
Fixed in
  • 2.3.8

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Froxlor to version 2.3.8 or later, where this vulnerability is fixed. No other mitigation is indicated or required as the fix addresses the root cause by properly filtering sensitive fields in API responses.

Description

CVE-2026-62988 is a critical vulnerability in Froxlor server administration software versions prior to 2.3.8. Certain API commands exposed full database rows including password hashes and Base32-encoded TOTP seeds without redaction. An authenticated user with API access can retrieve sensitive credentials and two-factor authentication secrets, enabling potential account takeover. The issue is fixed in version 2.3.8.

References

Community reviews

Loading reviews…