Quick answers
- Is CVE-2026-100709 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-100709 being exploited in the wild.
- How severe is CVE-2026-100709?
- High severity, with a CVSS score of 7.5, published 26 September 2026.
- Which products and versions are affected?
- Froxlor through 2.3.10.
- Is there a fix for CVE-2026-100709?
- A patch was published on 2026-09-26: fixed in version 2.3.12 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-100709 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-100709?
- Check whether you run Froxlor at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The panel_2fa_tokens table stores only a numeric user ID without recording whether the token belongs to a customer or administrator account, despite these IDs being allocated from separate namespaces. During login, the remembered-token lookup does not constrain results to the account type being authenticated, allowing a customer token with ID N to satisfy authentication for an administrator with ID N. The vulnerability requires the attacker to already possess both the target administrator's password and a valid remembered 2FA cookie from a customer account with a colliding ID; it is a second-factor bypass that does not defeat password authentication. The vulnerability is fixed in version 2.3.12.
Affected products
- Froxlor Froxlor through 2.3.10
Timeline
- 2026-09-26: disclosed
- 2026-09-26: patched: fixed in version 2.3.12