CVE-2026-100709 Froxlor before 2.3.11 2FA Bypass via Namespace Confusion
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- No known exploitation · automatable: no · technical impact: total
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.11.
Upgrade path
1 package: 1 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| froxlor | < 2.3.11 | 2.3.11 | Fixed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| froxlor | < 2.3.11 | 2.3.11 |
References
- GitHub Security Advisory (GHSA-9fq7-9w8p-c3qh) vendor-advisory
- VulnCheck Advisory: Froxlor before 2.3.11 2FA Bypass via Namespace Confusion third-party-advisory
- ENISA EUVD EUVD-2026-87682 third-party-advisory