Froxlor
Froxlor before 2.3.11 2FA Bypass via Namespace Confusion
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.11.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 2.3.11
Fixed in 2.3.11
Mitigation
Upgrade froxlor to 2.3.11 or later.
References
- Vendor advisory github.com/froxlor/froxlor/security/advisories…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.