Description
Froxlor through 2.3.10 stores only a numeric user ID in remembered-2FA tokens (panel_2fa_tokens) without recording the account namespace, and the remembered-token lookup during login is not constrained to the customer or administrator account type. Because customer and administrator IDs are allocated from separate namespaces, a remembered-2FA token legitimately issued to a customer with a given ID also matches an administrator with the same ID. An attacker who controls a customer account with a colliding ID, holds a valid remembered-2FA cookie for it, and already knows the target administrator's password can bypass the administrator's TOTP second factor and obtain an authenticated administrator session. This is a second-factor bypass only; it does not defeat password authentication. Fixed in 2.3.12.
Published: 2026-09-26
Score: 7.7 High
EPSS: < 1% Very Low
KEV: No
Impact: Second‑factor bypass via namespace collision
Action: Immediate Patch
AI Analysis

Impact

Froxlor versions prior to 2.3.12 generate a remembered‑2FA token that stores only the numeric user ID and omits the distinction between customer and administrator namespaces. When the login system verifies a token, it does not restrict the lookup to the correct account type, allowing a token issued to a customer account with a colliding numeric ID to be accepted for an administrator account of the same ID. An attacker who controls such a colliding customer account and has a valid remembered‑2FA cookie for that account can combine that cookie with a known administrator password to bypass the administrator’s TOTP second factor and gain an authenticated administrator session. The vulnerability does not compromise password authentication itself, but it removes the second‑factor protection for the affected administrators.

Affected Systems

The flaw resides in the Froxlor web hosting management interface and affects all Froxlor installations that are version 2.3.10 or earlier.

Risk and Exploitability

The CVSS score of 7.7 indicates a high severity of the flaw. EPSS data are not available, and the vulnerability has not been listed in the CISA KEV catalog. Exploitation requires the attacker to already possess a colliding customer account ID, a valid remembered‑2FA cookie for that account, and knowledge of an administrator’s password. While the conditions limit the attack to highly targeted scenarios, the possibility of bypassing second‑factor protection for administrators warrants a cautious approach. The likely attack vector is a web‑based login flow where the attacker leverages a stolen cookie and a known admin password to elevate privileges.

Generated by OpenCVE AI on September 26, 2026 at 16:26 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Froxlor to version 2.3.12 or later where namespace is enforced in remembered‑2FA tokens.
  • Delete all existing remembered‑2FA tokens after upgrading to clear potential conflicts.
  • Temporarily disable the ‘remember‑me’ 2FA option for administrative accounts until the namespace issue is resolved or until the token enforcement is verified.

Generated by OpenCVE AI on September 26, 2026 at 16:26 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sun, 27 Sep 2026 00:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Sat, 26 Sep 2026 13:30:00 +0000

Type Values Removed Values Added
Description Froxlor through 2.3.10 stores only a numeric user ID in remembered-2FA tokens (panel_2fa_tokens) without recording the account namespace, and the remembered-token lookup during login is not constrained to the customer or administrator account type. Because customer and administrator IDs are allocated from separate namespaces, a remembered-2FA token legitimately issued to a customer with a given ID also matches an administrator with the same ID. An attacker who controls a customer account with a colliding ID, holds a valid remembered-2FA cookie for it, and already knows the target administrator's password can bypass the administrator's TOTP second factor and obtain an authenticated administrator session. This is a second-factor bypass only; it does not defeat password authentication. Fixed in 2.3.12.
Title Froxlor before 2.3.12 2FA Bypass via Namespace Confusion
First Time appeared Froxlor
Froxlor froxlor
Weaknesses CWE-287
CPEs cpe:2.3:a:froxlor:froxlor:*:*:*:*:*:*:*:*
Vendors & Products Froxlor
Froxlor froxlor
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 7.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-09-26T23:08:21.420Z

Reserved: 2026-09-26T02:40:23.372Z

Link: CVE-2026-100709

cve-icon Vulnrichment

Updated: 2026-09-26T23:08:18.530Z

cve-icon NVD

Status : Deferred

Published: 2026-09-26T14:16:56.417

Modified: 2026-09-26T23:16:32.930

Link: CVE-2026-100709

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-26T17:15:14Z

Weaknesses