Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-f9rx-7wf7-jr36 | Froxlor's API Authentication bypasses 2FA Authentication |
Tue, 18 Aug 2026 22:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Froxlor
Froxlor froxlor |
|
| Vendors & Products |
Froxlor
Froxlor froxlor |
Tue, 18 Aug 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Froxlor: API Authentication bypasses 2FA Authentication | |
| Weaknesses | CWE-287 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-08-18T20:09:33.330Z
Reserved: 2026-06-08T18:02:19.731Z
Link: CVE-2026-52793
No data.
Status : Received
Published: 2026-08-18T21:16:34.650
Modified: 2026-08-18T21:16:34.650
Link: CVE-2026-52793
No data.
OpenCVE Enrichment
Updated: 2026-08-18T22:30:04Z
Github GHSA