Skip to main content

Froxlor CVE-2026-100709

| EUVDEUVD-2026-87682 HIGH
Improper Authentication (CWE-287)
2026-09-26 VulnCheck GHSA-pj38-8h4x-w384
7.7
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain target admin password (out of band)
  2. Delivery
    Control customer account with colliding ID
  3. Exploit
    Acquire valid remembered-2FA cookie for it
  4. Execution
    Submit admin password at login
  5. Persist
    Present customer token, cross-namespace lookup accepts
  6. Impact
    Authenticated administrator session (2FA bypassed)

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication mechanism validation
MITRE ATT&CK

2 techniques across 2 tactics: Defense Evasion, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires ALL of the following to hold simultaneously: (1) the attacker already knows the target administrator's password - this vuln only defeats the TOTP second factor, never password authentication; (2) the attacker controls a customer account whose numeric ID collides with the target administrator's ID, exploiting that customer and administrator IDs are allocated from separate namespaces while the remembered-2FA token (panel_2fa_tokens) stores only the bare numeric ID with no account-type namespace; (3) the attacker possesses a valid remembered-2FA cookie legitimately issued to that customer account. The exploitation vector is the login-time remembered-token lookup, which is not constrained to the customer-vs-administrator account type. Limiting factors: the mandatory prior password compromise, the need for an ID collision (not always achievable), and possession of a live remembered cookie make this a chained, targeted attack rather than a default-config remote takeover.

Impact

The vendor scores this 7.7 (CVSS 4.0, AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H), which is directionally reasonable but arguably generous on complexity. The exploit is not a standalone remote takeover: it is a second-factor-only bypass that presupposes the attacker ALREADY knows the target administrator's password, ALREADY controls a customer account whose numeric ID collides with that administrator's ID, and ALREADY holds a valid remembered-2FA cookie legitimately issued to that customer account. The AT:P (Present attack requirement) captures the ID-collision precondition, but the combination of password knowledge + colliding-ID account + valid remembered cookie is substantial and, in my view, closer to high attack complexity. No EPSS score, no CISA KEV listing, and no public exploit code are present in the input, so this is 'no public exploit identified at time of analysis' - not active exploitation. There is no SSVC decision data supplied. Net: the impact IS severe (full administrator session on a panel that manages all tenants), but the multiple stacked preconditions make this a targeted, chained-attack issue rather than a mass-exploitable one. The realistic priority is moderate: patch it, but the password-precondition means it cannot be the sole entry point.

Exploit ScenarioDerived

An attacker who has already phished or otherwise obtained a Froxlor administrator's password registers or controls a customer account whose numeric ID equals that administrator's ID, and obtains a remembered-2FA cookie for the customer account. At the admin login the attacker supplies the known password and presents the customer's remembered-2FA token, which the unconstrained lookup accepts across the account-type boundary, granting an authenticated administrator session without the TOTP second factor. No public exploit code is identified in the provided data.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 26, 2026

Second-factor bypass in Froxlor through 2.3.10 allows an attacker who already knows a target administrator's password to defeat the administrator's TOTP protection and obtain a full authenticated admin session. The flaw is rooted in remembered-2FA tokens (panel_2fa_tokens) storing only a bare numeric user ID with no account-type namespace; because customer and administrator IDs are drawn from separate sequences, a remembered-2FA cookie issued to a customer can satisfy the login-time token lookup for an administrator with the same numeric ID, which is not constrained by account type. Exploitation is chained and targeted: it requires prior password compromise, control of a customer account whose ID collides with the target admin, and a live remembered-2FA cookie, so this is not a default-config remote takeover; no public exploit code was identified at time of analysis, and the issue is fixed in 2.3.12 (per the CVSS 4.0 vector, PR:L).

RemediationAI

Upgrade Froxlor to 2.3.12 or later, the vendor-released fix that namespaces remembered-2FA tokens to the correct account type and constrains the login-time lookup; details are in the GitHub advisory at https://github.com/froxlor/froxlor/security/advisories/GHSA-9fq7-9w8p-c3qh and the VulnCheck advisory at https://www.vulncheck.com/advisories/froxlor-before-2.3.12-2fa-bypass-via-namespace-confusion. If immediate upgrade is not possible, purge the panel_2fa_tokens table (or delete remembered-2FA cookies for all users) to invalidate colliding tokens and force TOTP entry on next login - the trade-off is that every user must re-enroll a remembered device; disabling the 'remember this device' 2FA feature entirely removes the attack path at the cost of forcing TOTP on every login. Because the bypass still requires a valid administrator password, rotate all privileged credentials and audit administrator accounts for signs of prior compromise, and consider restricting panel login to trusted networks or placing it behind a VPN or IP allowlist, which reduces exposure but does not fix the underlying token-namespace flaw. Note that customer-versus-administrator ID alignment is systemic in the default schema, so configuration-only mitigations cannot eliminate the collision condition on their own; the 2.3.12 upgrade is the only complete remedy.

Affected VersionsENISA

Froxlor 0 <2.3.12

Affected Packages

euvd froxlor fix: 2.3.12

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Froxlor is a self-hosted web hosting control panel that separates customer accounts from administrator accounts, allocating each type from its own numeric ID namespace. When a user enables 'remember this device' for two-factor authentication, the resulting token is persisted in the panel_2fa_tokens table keyed by that numeric ID alone, with no discriminator recording whether the subject is a customer or an administrator. At login, the remembered-token lookup is likewise not scoped to the account type, so a token legitimately created for customer ID N will match administrator ID N when that administrator authenticates. This is a classic authentication-schema design error mapped to CWE-287 (Improper Authentication): the identity key is non-unique across the two trust domains, causing a namespace-confusion collision. The result is a pure second-factor bypass - password verification still occurs, so the attacker must already hold valid administrator credentials - but possession of the colliding remembered cookie lets the login complete without presenting the admin's TOTP code. CPE cpe:2.3:a:froxlor:froxlor:*:*:*:*:*:*:*:* covers the affected Froxlor product line, and the ENISA EUVD entry (EUVD-2026-87682) records affected versions as 0 through 2.3.12 exclusive. The vendor scored this 7.7 under CVSS 4.0 (AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H), which is directionally reasonable but arguably generous on complexity given the mandatory prior password compromise, the ID-collision precondition, and the need for a live remembered cookie; our independent CVSS 3.1 assessment rates it AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H.

Know when Froxlor gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 7.7 HIGH
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
vuln.today AI 8.5 HIGH

AC:H because success requires a colliding customer ID, a valid pre-issued remembered cookie, and prior password knowledge; PR:L for the needed customer account; S:C as it crosses into the admin/tenant-management authority; full C/I/A on the panel.

3.1 AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch available
Sep 26, 2026 - 14:02 EUVD
CVE Published
Sep 26, 2026 - 13:24 cve.org
HIGH 7.7

DescriptionCVE.org

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.

Technical POC Analysis

CWE-287 (Improper Authentication) - an account-namespace confusion in Froxlor's remembered-2FA feature.

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

Froxlor versions through 2.3.10 contain a high-severity second-factor bypass that can undermine TOTP protection for administrator accounts, potentially giving an attacker full control of the hosting panel and its customer and service data. Exploitation is not a default remote takeover: it requires prior administrator password compromise, a customer account whose numeric ID matches the target administrator, and a valid remembered-2FA cookie, and no public exploit identified at time of analysis. Leadership should prioritize patching because a successful bypass would grant authenticated administrative access and could affect hosted services, customer data, and operational trust.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 81% exploitable
Prevalence
Low
Froxlor is a niche open-source PHP web-hosting control panel
Data Quality
4 sources
Confidence: Medium
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2023-0315 HIGH POC
8.8 Jan 16

Command Injection in GitHub repository froxlor/froxlor prior to 2.0.8. Rated high severity (CVSS 8.8), this vulnerabilit

CVE-2023-3173 CRITICAL POC
9.8 Jun 09

Improper Restriction of Excessive Authentication Attempts in GitHub repository froxlor/froxlor prior to 2.0.20. Rated cr

CVE-2023-1307 CRITICAL POC
9.8 Mar 10

Authentication Bypass by Primary Weakness in GitHub repository froxlor/froxlor prior to 2.0.13. Rated critical severity

CVE-2021-42325 CRITICAL POC
9.8 Oct 12

Froxlor through 0.10.29.1 allows SQL injection in Database/Manager/DbManagerMySQL.php via a custom DB name. Rated critic

CVE-2026-26279 CRITICAL POC
9.1 Mar 03

Command injection in Froxlor server admin before 2.3.4 due to typo (== instead of =) disabling input validation entirely

CVE-2023-6069 HIGH POC
8.8 Nov 10

Improper Link Resolution Before File Access in GitHub repository froxlor/froxlor prior to 2.1.0. Rated high severity (CV

CVE-2023-2034 HIGH POC
8.8 Apr 14

Unrestricted Upload of File with Dangerous Type in GitHub repository froxlor/froxlor prior to 2.0.14. Rated high severit

CVE-2023-1033 HIGH POC
8.8 Feb 25

Cross-Site Request Forgery (CSRF) in GitHub repository froxlor/froxlor prior to 2.0.11. Rated high severity (CVSS 8.8),

CVE-2023-0877 HIGH POC
8.8 Feb 17

Code Injection in GitHub repository froxlor/froxlor prior to 2.0.11. Rated high severity (CVSS 8.8), this vulnerability

CVE-2023-0671 HIGH POC
8.8 Feb 04

Code Injection in GitHub repository froxlor/froxlor prior to 2.0.10. Rated high severity (CVSS 8.8), this vulnerability

CVE-2020-10235 HIGH POC
8.8 Mar 09

An issue was discovered in Froxlor before 0.10.14. Rated high severity (CVSS 8.8), this vulnerability is remotely exploi

CVE-2023-50256 HIGH POC
7.5 Jan 03

Froxlor is open source server administration software. Rated high severity (CVSS 7.5), this vulnerability is remotely ex

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy