Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
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
|
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-09-26T13:24:02.908Z
Reserved: 2026-09-26T02:40:23.372Z
Link: CVE-2026-100709
No data.
Status : Deferred
Published: 2026-09-26T14:16:56.417
Modified: 2026-09-26T14:16:56.530
Link: CVE-2026-100709
No data.
OpenCVE Enrichment
Updated: 2026-09-26T16:30:07Z
-
CWE-287
Improper Authentication