CyberRota Analysis
AI-GeneratedFroxlor versions prior to 2.3.7 are vulnerable due to inadequate two-factor authentication (2FA) checks in the API authentication process, allowing attackers with valid API keys and secrets to bypass 2FA and access sensitive data. This flaw can lead to unauthorized exposure or modification of customer data, domains, and other critical resources. Organizations using Froxlor should prioritize upgrading to version 2.3.7 to mitigate this high-severity risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD 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.