Servers and applications
CVE-2026-52793
API Authentication bypasses 2FA Authentication
- Severity
- High 8.1
- Published
- 29 May 2026
- Last changed
- 8 Jun 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 2.3.7
- Exploit chance
- 0.3% in the next 30 daysHigher than 26% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Read data · Change data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N- Also known as
- GHSA-f9rx-7wf7-jr36
- Sources
- Project advisories (GitHub)
Description
Froxlor's API authentication (FroxlorRPC::validateAuth) does not enforce Two-Factor Authentication. When a user (admin or customer) enables 2FA on their account, the web UI correctly requires a TOTP code after password verification. However, the API accepts requests authenticated with only an API key and secret — no TOTP challenge is issued, checked, or required.
An attacker who obtains a leaked API key+secret for a 2FA-protected account has full access to all API operations without providing a second factor.
Result: Redirect to index.php?showmessage=4 — 2FA page. Login is NOT completed. The user cannot access the dashboard without entering a TOTP code.
Result: HTTP 200 with full customer listing:
No TOTP code was provided. No 2FA prompt was returned. Full access granted.
When a user enables 2FA, they expect all access to their account requires a second factor. The API completely bypasses this expectation:
Affected software
| Software | Affected versions |
|---|---|
FroxlorServers and applications · github:froxlor/froxlor |
|
About Froxlor
The server administration software for your needs - The official Froxlor development Git repository
- Monthly downloads (Packagist)
- 159Packagist, 15 Nov 2026
- Total downloads (Packagist)
- 406Packagist, 15 Nov 2026
- GitHub stars
- 1,752GitHub, 15 Nov 2026
- Forks
- 467GitHub, 15 Nov 2026
- Latest release
- 2.3.17GitHub, 15 Nov 2026
- Released
- 8 Nov 2026GitHub
- License
- GNU Lesser General Public License, version 2.1Wikidata
- Written in
- PHPWikidata
- First published on GitHub
- 6 Mar 2012GitHub
Vulnerabilities in Froxlor
- In our list
- 97
- Published in the last 12 months
- 56
- Critical, last 12 months
- 6
- High, last 12 months
- 24
- Known exploited
- 0
- CVE-2026-130755Froxlor before 2.3.16 Authorization Bypass via Traffic.listing API CommandMedium 5.3 18 Nov 2026
- CVE-2026-121436Froxlor 2.3.8 before 2.3.15 API Key Disclosure via api_keys.phpHigh 8.6 3 Nov 2026
- CVE-2026-121435Froxlor before 2.3.15 Authorization Bypass via Mysqls.add APIMedium 5.3 3 Nov 2026
- CVE-2026-121434Froxlor 2.3.0 before 2.3.15 Authorization Bypass via Certificates.update APIMedium 5.3 3 Nov 2026
- GHSA-vhfr-xvmw-p2m9Froxlor customer Traffic listing API bypasses the customer_hide_options traffic restrictionMedium 4.3 3 Nov 2026
- CVE-2026-113678Froxlor before 2.3.15 Symlink Following Privilege Escalation via Traffic CronCritical 9.4 20 Oct 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-52793
- GitHub Advisory Database https://github.com/advisories/GHSA-f9rx-7wf7-jr36
- github.com https://github.com/froxlor/froxlor/security/advisories/GHSA-f9rx-7wf7-jr36