---
id: CVE-2026-100709
title: >-
  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 ac…
summary: >-
  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 ac…
severity: high
cvss: 7.5
cvssVector: 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'
cwe:
  - CWE-287
vendor: froxlor
product: froxlor
affected:
  - froxlor < 2.3.12
published: '2026-09-26'
updated: '2026-09-26'
sourceUpdated: '2026-09-26T23:16:32.930'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-100709'
references:
  - url: 'https://github.com/froxlor/froxlor/security/advisories/GHSA-9fq7-9w8p-c3qh'
    label: disclosure@vulncheck.com
  - url: >-
      https://www.vulncheck.com/advisories/froxlor-before-2.3.12-2fa-bypass-via-namespace-confusion
    label: disclosure@vulncheck.com
tags:
  - nvd
  - cve.org
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: total
  timestamp: '2026-09-26T23:08:11.816656Z'
ingestedAt: '2026-09-26T13:33:20.897Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.