Cross-Site Request Forgery (CSRF) in froxlor (CVE-2026-100712)
Summary
Vulnerability in froxlor (CVE-2026-100712). Data can be tampered with by attackers. Mitigation: upgrade to 2.3.12 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-100712 has been found in froxlor.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade froxlor to 2.3.12 or later.
If unsure, ask your IT team or search "froxlor CVE-2026-100712" on the vendor's site.
CVE-2026-100712 (froxlor) — CWE-352 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated
Patched: 2.3.12 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
CSRF (CWE-352) exists in froxlor.
Check the vendor advisory for the affected versions of froxlor.
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.
Update to 2.3.12.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'froxlor' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'froxlor' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
froxlorを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade froxlor to 2.3.12ステージング環境で 2.3.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web github.com
- web vulncheck.com
- web nvd.nist.gov
- web github.com