# CVE-2026-100709: Froxlor TOTP bypass via 2FA token namespace confusion

Source: https://junglewise.ai/threats/cve-2026-100709-froxlor-through-2-3-10-stores-only-a-numeric-user-id-in  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-26. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-100709 · Severity: high · CVSS 7.5 · Published 2026-09-26

Froxlor is a web hosting control panel that manages customer and administrator accounts. An attacker who knows an administrator's password and controls a customer account with a matching numeric ID can bypass the administrator's two-factor authentication (TOTP) by reusing the customer's remembered 2FA token, gaining full administrative access to the panel including all customer data and configuration.

Technologies: [Froxlor](https://junglewise.ai/threats/technologies/froxlor). Vendors: [Froxlor](https://junglewise.ai/threats/vendors/froxlor).

## 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

## References

- [https://github.com/froxlor/froxlor/security/advisories/GHSA-9fq7-9w8p-c3qh](https://github.com/froxlor/froxlor/security/advisories/GHSA-9fq7-9w8p-c3qh)
- [https://www.vulncheck.com/advisories/froxlor-before-2.3.12-2fa-bypass-via-namespace-confusion](https://www.vulncheck.com/advisories/froxlor-before-2.3.12-2fa-bypass-via-namespace-confusion)

## Related threats

- [Froxlor information disclosure in API keys listing](https://junglewise.ai/threats/cve-2026-121436-froxlor-from-2-3-8-before-2-3-15-contains-an-information)
- [Froxlor authorization bypass in Mysqls.add API](https://junglewise.ai/threats/cve-2026-121435-froxlor-before-2-3-15-contains-an-authorization-bypass)
- [Froxlor Certificates API authorization bypass in Let's Encrypt management](https://junglewise.ai/threats/cve-2026-121434-froxlor-2-3-0-before-2-3-15-contains-a-missing-authorization)
- [Froxlor symlink following in Statistics::makeChownWithNewStats](https://junglewise.ai/threats/cve-2026-113678-froxlor-before-2-3-15-contains-a-symlink-following-vulnerability)
- [Froxlor missing authorization in SubDomains.delete API](https://junglewise.ai/threats/cve-2026-113677-froxlor-from-0-10-0-before-2-3-15-contains-a-missing)