CVE-2026-100712 froxlor before 2.3.12 Two-Factor Authentication Bypass via CSRF

High 7.1 Published Updated

Attackers can bypass two-factor authentication via CSRF, reducing accounts to password-only protection and enabling potential account takeover.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
None listed

What is CVE-2026-100712?

CVE-2026-100712 is a high-severity vulnerability in froxlor, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

Official description

froxlor through 2.3.10 disables a user's two-factor authentication immediately upon an unauthenticated-triggerable GET request to the 2FA management page (e.g. /customer_index.php?page=2fa&action=delete), with no confirmation, re-authentication, or CSRF token. The global CSRF middleware only covers POST/PUT/PATCH/DELETE requests, and the session cookie is set to SameSite=Lax, so a cross-site top-level navigation (link click or redirect) carries the victim's session and silently clears type_2fa/data_2fa. Both the customer and admin 2FA handlers are affected. An attacker who lures a logged-in panel user into following a crafted link reduces that account to password-only authentication, which can be chained with a compromised password for account takeover. Fixed in 2.3.12.

Weakness: CWE-352

Which versions are affected by CVE-2026-100712?

How do I fix CVE-2026-100712?

No fix has been published for CVE-2026-100712 yet. Limit exposure of the affected software until one is available.

Is CVE-2026-100712 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100712 exists.

Sources

Also known as GHSA-c94r-x438-wxmw, GHSA-w582-7wqv-62mm.

Is CVE-2026-100712 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free