Servers and applications
CVE-2026-100709
Froxlor remembered-2FA account namespace confusion
- Severity
- High 7.7
- Published
- 6 Sept 2026
- Last changed
- 26 Oct 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 2.3.12
- Exploit chance
- 0.3% in the next 30 daysHigher than 21% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · Only under certain conditions · Needs a user account · No user action needed
- Attacker can
- Read data · Change data · Take it down
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N- Also known as
- GHSA-9fq7-9w8p-c3qh
- Sources
- Project advisories (GitHub)
Description
Remembered-2FA tokens store only a numeric user ID although customer and administrator IDs occupy separate namespaces. With equal IDs, a valid customer remember token can satisfy an administrator's TOTP step after the attacker supplies that administrator's correct password.
Froxlor resolves a submitted username and password to either a customer row or an administrator row before checking remembered 2FA. Both tables allocate their own numeric primary keys, so customer ID 1 and administrator ID 1 can legitimately exist at the same time. The affected panel_2fa_tokens schema stores a selector, hashed authenticator, numeric userid, and expiration, but does not store the account namespace that issued the token.
During login, the remembered-token query uses the cookie selector and the numeric ID from the newly resolved account. It does not constrain the lookup to the customer or administrator account type.
Affected software
| Software | Affected versions |
|---|---|
FroxlorServers and applications · github:froxlor/froxlor |
|
About Froxlor
The server administration software for your needs - The official Froxlor development Git repository
- Monthly downloads (Packagist)
- 159Packagist, 15 Nov 2026
- Total downloads (Packagist)
- 406Packagist, 15 Nov 2026
- GitHub stars
- 1,752GitHub, 15 Nov 2026
- Forks
- 467GitHub, 15 Nov 2026
- Latest release
- 2.3.17GitHub, 15 Nov 2026
- Released
- 8 Nov 2026GitHub
- License
- GNU Lesser General Public License, version 2.1Wikidata
- Written in
- PHPWikidata
- First published on GitHub
- 6 Mar 2012GitHub
Vulnerabilities in Froxlor
- In our list
- 97
- Published in the last 12 months
- 56
- Critical, last 12 months
- 6
- High, last 12 months
- 24
- Known exploited
- 0
- CVE-2026-130755Froxlor before 2.3.16 Authorization Bypass via Traffic.listing API CommandMedium 5.3 18 Nov 2026
- CVE-2026-121436Froxlor 2.3.8 before 2.3.15 API Key Disclosure via api_keys.phpHigh 8.6 3 Nov 2026
- CVE-2026-121435Froxlor before 2.3.15 Authorization Bypass via Mysqls.add APIMedium 5.3 3 Nov 2026
- CVE-2026-121434Froxlor 2.3.0 before 2.3.15 Authorization Bypass via Certificates.update APIMedium 5.3 3 Nov 2026
- GHSA-vhfr-xvmw-p2m9Froxlor customer Traffic listing API bypasses the customer_hide_options traffic restrictionMedium 4.3 3 Nov 2026
- CVE-2026-113678Froxlor before 2.3.15 Symlink Following Privilege Escalation via Traffic CronCritical 9.4 20 Oct 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-100709
- GitHub Advisory Database https://github.com/advisories/GHSA-9fq7-9w8p-c3qh
- github.com https://github.com/froxlor/froxlor/security/advisories/GHSA-9fq7-9w8p-c3qh