Skip to content
Applications

CVE-2026-62988

9.0
Critical
EPSS 0.68%Patch availableAug 19, 2026

Froxlor API leaks password hashes and TOTP seeds enabling account takeover.

common questions

Is CVE-2026-62988 being exploited?

Not confirmed. CVE-2026-62988 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.68% probability of exploitation in the next 30 days.

How severe is CVE-2026-62988?

CVE-2026-62988 is rated Critical with a CVSS score of 9.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-62988?

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

What does CVE-2026-62988 affect?

CVE-2026-62988 affects Froxlor < 2.3.8, API endpoints: Customers.get, Customers.listing, Admins.get, Admins.listing, Ftps.get, Ftps.listing. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-62988?

Upgrade to Froxlor 2.3.8+, rotate passwords and reset TOTP for all accounts.

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

executive summary
technical analysis
affected
Froxlor < 2.3.8API endpoints: Customers.get, Customers.listing, Admins.get, Admins.listing, Ftps.get, Ftps.listing
impact

Authenticated API callers can retrieve password hashes and Base32 TOTP seeds, enabling offline cracking and 2FA bypass to take over admin/customer/FTP accounts.

action required

Immediate action required

affected versions
froxlor froxlor
  • affected< 2.3.8

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