EUVD-2026-61215
GHSA-f9rx-7wf7-jr36
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Requires a valid API key (PR:L) over network (AV:N); no complexity beyond credential possession; full read/write over hosting data (C:H/I:H) but no availability impact (A:N).
Primary rating from Vendor (github).
CVSS VectorVendor: github
Lifecycle Timeline
3DescriptionCVE.org
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.
AnalysisAI
Two-Factor Authentication is fully bypassed in Froxlor's API layer (versions prior to 2.3.7), allowing any holder of a valid API key and secret to invoke all API operations - including management of domains, DNS records, SSL certificates, email, FTP, and databases - without supplying the configured TOTP code. The web UI enforces 2FA correctly via FroxlorTwoFactorAuth::verifyCode(), but the API authentication function FroxlorRPC::validateAuth in lib/Froxlor/Api/FroxlorRPC.php checks only key validity, expiration, API permission, and account status, with zero references to 2FA logic across the entire lib/Froxlor/Api/ directory. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Three concrete conditions must be met simultaneously: (1) The Froxlor API must be enabled - `api.enabled=1` is a non-default configuration requiring explicit administrator action in the panel settings; (2) The targeted account (admin or customer) must have 2FA enabled (`type_2fa != 0`) - accounts without 2FA configured are not additionally at risk from this specific bypass since 2FA is the only bypassed control; (3) The attacker must hold a valid, unexpired API key and secret for the targeted account - these are cryptographically strong random values (SHA-256 and SHA-512 of 64×64 and 64×64×4 bytes of random data respectively) and are not guessable by brute force, so they must be obtained through a separate compromise vector such as a database breach, exposed backup, secrets manager misconfiguration, or insider access. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N scores 8.1 and accurately represents the threat model: the attack is network-accessible with no complexity or user interaction, but requires low-privilege credentials (a valid API key+secret, hence PR:L) that must be separately obtained. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Upgrade Froxlor to version 2.3.7 or later, available at https://github.com/froxlor/froxlor/releases/tag/2.3.7 and via Composer. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, immediately audit Froxlor API access logs for suspicious activity patterns, rotate any potentially compromised API keys, and restrict API access to only necessary IP addresses. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it
sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not
(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear
The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by
ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C
Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au
Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c
Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
Same weakness CWE-287 – Improper Authentication
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today