CVE-2026-62988: Froxlor: Credential and 2FA secret disclosure via Froxlor API endpoints
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.
Security readout for executives and security teams
Plain-English summary
Froxlor 2.3.7 can expose password hashes and two-factor authentication secrets to an authenticated API user permitted to call affected endpoints. Stolen hashes may be cracked offline, while exposed TOTP seeds can produce valid verification codes. Together, these disclosures could enable hosting-panel or hosted-resource takeover.
Executive priority
Treat as an urgent credential-exposure incident for any affected deployment. Upgrade promptly, determine who could call the vulnerable APIs, review historical access, and rotate potentially disclosed credentials and TOTP secrets. Prioritize internet-accessible or multi-administrator hosting environments because compromise could affect both the control panel and hosted resources.
Technical view
Affected customer, administrator, and FTP API get/listing commands return full database rows without removing password and data_2fa fields. Exploitation requires authenticated API access and permission for an affected endpoint. The flaw is remotely reachable, needs no victim interaction, and crosses authorization boundaries by exposing credentials belonging to other accounts.
Likely exposure
Froxlor deployments running version 2.3.7 before 2.3.8 are exposed when authenticated API callers can access the affected Customers, Admins, or Ftps get/listing commands. Risk depends on API enablement, caller permissions, and whether those endpoints were invoked. The supplied evidence does not identify exposed installations.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not listed as KEV in the bundle. Abuse nevertheless has serious consequences because disclosed password hashes support offline cracking and disclosed TOTP seeds remain usable until two-factor authentication is reset.
Researcher notes
CVSS 3.1 is 9.0: network-accessible, low-complexity exploitation with high privileges, no user interaction, changed scope, and high confidentiality and integrity impact. CWE-200 applies. The evidence supports credential and TOTP-secret disclosure, but does not establish public exploitation, affected-installation counts, or compromise indicators.
Mitigation direction
Upgrade Froxlor to version 2.3.8 or later.
Reset TOTP enrollment for potentially exposed administrator and customer accounts.
Rotate potentially exposed administrator, customer, and FTP passwords.
Review and restrict permissions for callers allowed to use affected API endpoints.
Revoke or rotate API credentials if unauthorized access is suspected.
Validation and detection
Confirm the deployed Froxlor version is 2.3.8 or later.
Inventory accounts and integrations permitted to call the affected API commands.
Review API and authentication logs for unexpected access to affected endpoints.
Verify potentially exposed passwords and TOTP enrollments were rotated.
Confirm affected responses no longer contain password or data_2fa fields.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-200 · source CWE mapping
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.