CVEvulnerability
CVE-2026-52793
8.1 HIGH
Official page ↗
- Status
- Deferred
- Published
- 2026-08-18
- Last modified
- 2026-09-08
- Assigner
- [email protected]
- CVSS 3.1 ([email protected])
- 8.1 HIGH — CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
- Weaknesses
- CWE-287
Description
Froxlor is open source server administration software. Prior to 2.3.7, the API authentication path in lib/Froxlor/Api/FroxlorRPC.php and FroxlorRPC::validateAuth accepts an API key and secret for an administrator or customer account without checking type_2fa, validating a TOTP code, or invoking FroxlorTwoFactorAuth. The web interface requires a second factor for accounts with two-factor authentication enabled, but the API grants access after validating only the API credentials, expiration, API permission, and account status. An attacker who obtains an API key and secret for a protected account can call the available API functions without supplying the configured second factor, which can expose or modify customer data, domains, email and FTP accounts, databases, DNS records, and certificate material. This issue is fixed in version 2.3.7.
Related
Weakness · CWE (1)
- CWE-287 Improper Authentication weakness
References
- https://github.com/froxlor/froxlor/commit/7fc21dc6f8d22673e4ddc765b710c9d3f85cb001 github.com
- https://github.com/froxlor/froxlor/releases/tag/2.3.7 github.com
- https://github.com/froxlor/froxlor/security/advisories/GHSA-f9rx-7wf7-jr36 github.com
- https://github.com/froxlor/froxlor/security/advisories/GHSA-f9rx-7wf7-jr36 github.com