8.1
HIGH CVSS 3.1
CVE-2026-52793
Froxlor: API Authentication bypasses 2FA Authentication
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.

INFO

Published Date :

Aug. 18, 2026, 9:16 p.m.

Last Modified :

Aug. 19, 2026, 4:17 p.m.

Remotely Exploit :

Yes !
Affected Products

The following products are affected by CVE-2026-52793 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Froxlor froxlor
CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 134c704f-9b21-4f2e-91b3-4a467353bcc0
CVSS 3.1 HIGH [email protected]
CVSS 3.1 HIGH MITRE-CVE
Solution
Update Froxlor to version 2.3.7 to enforce API authentication for two-factor enabled accounts.
  • Update Froxlor to version 2.3.7.
  • Ensure API authentication enforces two-factor if enabled.
References to Advisories, Solutions, and Tools
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-52793 is associated with the following CWEs:

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-52793 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-52793 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0

    Aug. 19, 2026

    Action Type Old Value New Value
    Added Reference https://github.com/froxlor/froxlor/security/advisories/GHSA-f9rx-7wf7-jr36
    Added SSVC {'id': 'CVE-2026-52793', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'poc'}, {'automatable': 'no'}, {'technicalImpact': 'total'}], 'version': '2.0.3', 'timestamp': '2026-08-19T15:23:09.833159Z'}
  • New CVE Received by [email protected]

    Aug. 18, 2026

    Action Type Old Value New Value
    Added Affected [{'vendor': 'froxlor', 'product': 'froxlor', 'versions': [{'status': 'affected', 'version': '<.3.7'}]}]
    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.
    Added CVSS V3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
    Added CWE CWE-287
    Added Reference https://github.com/froxlor/froxlor/commit/7fc21dc6f8d22673e4ddc765b710c9d3f85cb001
    Added Reference https://github.com/froxlor/froxlor/releases/tag/2.3.7
    Added Reference https://github.com/froxlor/froxlor/security/advisories/GHSA-f9rx-7wf7-jr36
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.