froxlor through 2.3.10 disables a user's two-factor authentication immediately upon an unauthenticated-triggerable GET request to the 2FA management… (CVE-2026-100712)
froxlor versions up to 2.3.10 contain a vulnerability where an unauthenticated GET request to the two-factor authentication (2FA) management page disables a user's 2FA without confirmation or re-authentication. This occurs because the global CSRF protection does not cover GET requests, and the session cookie's SameSite=Lax setting allows cross-site navigation to carry the session, enabling silent 2FA disablement. Both customer and admin 2FA handlers are affected. The issue is fixed in version 2.3.12.
AI Analysis
Technical Summary
froxlor through version 2.3.10 has a vulnerability (CVE-2026-100712) that allows an attacker to disable a logged-in user's two-factor authentication by triggering an unauthenticated GET request to the 2FA management endpoint (e.g., /customer_index.php?page=2fa&action=delete). The lack of CSRF protection on GET requests combined with the SameSite=Lax cookie setting enables cross-site top-level navigation to carry the victim's session and silently clear 2FA data without user confirmation or re-authentication. Both customer and admin 2FA handlers are vulnerable. This reduces account security to password-only authentication, which can be exploited if the password is compromised. The vulnerability is fixed in froxlor version 2.3.12.
Potential Impact
An attacker can lure a logged-in froxlor panel user to visit a crafted link that disables the user's two-factor authentication silently and without consent. This reduces the account's security to password-only authentication, increasing the risk of account takeover if the password is compromised. Both customer and admin accounts are affected, potentially allowing attackers to escalate privileges or gain unauthorized access.
Mitigation Recommendations
Upgrade froxlor to version 2.3.12 or later, where this vulnerability is fixed. Until then, users should be cautious about following untrusted links while logged into froxlor panels. There is no indication that additional mitigations such as configuration changes or workarounds are available.
froxlor through 2.3.10 disables a user's two-factor authentication immediately upon an unauthenticated-triggerable GET request to the 2FA management… (CVE-2026-100712)
Description
froxlor versions up to 2.3.10 contain a vulnerability where an unauthenticated GET request to the two-factor authentication (2FA) management page disables a user's 2FA without confirmation or re-authentication. This occurs because the global CSRF protection does not cover GET requests, and the session cookie's SameSite=Lax setting allows cross-site navigation to carry the session, enabling silent 2FA disablement. Both customer and admin 2FA handlers are affected. The issue is fixed in version 2.3.12.
CVSS v3.1
Score 6.5medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
froxlor through version 2.3.10 has a vulnerability (CVE-2026-100712) that allows an attacker to disable a logged-in user's two-factor authentication by triggering an unauthenticated GET request to the 2FA management endpoint (e.g., /customer_index.php?page=2fa&action=delete). The lack of CSRF protection on GET requests combined with the SameSite=Lax cookie setting enables cross-site top-level navigation to carry the victim's session and silently clear 2FA data without user confirmation or re-authentication. Both customer and admin 2FA handlers are vulnerable. This reduces account security to password-only authentication, which can be exploited if the password is compromised. The vulnerability is fixed in froxlor version 2.3.12.
Potential Impact
An attacker can lure a logged-in froxlor panel user to visit a crafted link that disables the user's two-factor authentication silently and without consent. This reduces the account's security to password-only authentication, increasing the risk of account takeover if the password is compromised. Both customer and admin accounts are affected, potentially allowing attackers to escalate privileges or gain unauthorized access.
Mitigation Recommendations
Upgrade froxlor to version 2.3.12 or later, where this vulnerability is fixed. Until then, users should be cautious about following untrusted links while logged into froxlor panels. There is no indication that additional mitigations such as configuration changes or workarounds are available.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-c94r-x438-wxmw
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-100712"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6ab89bd9f7a7c5410694201a
Added to database: 09/27/2026, 04:30:17 UTC
Last enriched: 09/27/2026, 04:40:59 UTC
Last updated: 09/28/2026, 01:47:40 UTC
Views: 17
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.