Vulnerability 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.
CVSS Score
HIGH
Related Weaknesses (CWE)
References
- https://github.com/froxlor/froxlor/commit/7fc21dc6f8d22673e4ddc765b710c9d3f85cb0
- https://github.com/froxlor/froxlor/releases/tag/2.3.7
- https://github.com/froxlor/froxlor/security/advisories/GHSA-f9rx-7wf7-jr36
- https://github.com/froxlor/froxlor/security/advisories/GHSA-f9rx-7wf7-jr36
FAQ
What is CVE-2026-52793?
CVE-2026-52793 is a vulnerability with a CVSS score of 8.1 (HIGH). 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 a...
How severe is CVE-2026-52793?
CVE-2026-52793 has been rated HIGH with a CVSS base score of 8.1/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-52793?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.