CVE-2026-100709

published 26 Sep 2026 · updated 29 Oct 2026

Froxlor before 2.3.11 2FA Bypass via Namespace Confusion

7.5HighCVSS 7.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 2.3.11.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
froxlor<2.3.112.3.11

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-100709 severity on Zeptric[![CVE-2026-100709](https://zeptric.io/badge/cve/CVE-2026-100709.svg)](https://zeptric.io/cve/CVE-2026-100709)