CVE-2026-100709Froxlor before 2.3.12 2FA Bypass via Namespace Confusion
Updated under an hour ago ()
Does this affect you?
It affects froxlor. Add what you run to find out whether that includes you.
EPSS puts the chance of exploitation in the next 30 days at 0.29%, higher than 19% of scored CVEs.
Do this next
Free account, 1 product
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.
- CVSS
- 7.5 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- CWE-287
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- 0.29% (percentile 19)
- Assigned by
- VulnCheck
- NVD analysis
- Deferred
- Record last updated
- Sep 26, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
froxlor froxlor froxlor:froxlor (from the name) | before 2.3.12; 2.3.12 not affected | CNA record |
References
- https://github.com/froxlor/froxlor/security/advisories/GHSA-9fq7-9w8p-c3qhvendor-advisory
- https://www.vulncheck.com/advisories/froxlor-before-2.3.12-2fa-bypass-via-namespace-confusionthird-party-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.