CVE-2026-100709: Froxlor before 2.3.11 2FA Bypass via Namespace Confusion

Severity: high (CVSS 7.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.3% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2026-09-26 · updated 2026-10-29
Weakness: CWE-287

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.

Affected products

froxlor: before 2.3.11 — fixed in 2.3.11

How to fix

Upgrade to a fixed version: froxlor 2.3.11. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-100709 or the next vulnerability affects your stack