Vulnerability in Froxlor (CVE-2026-100718)
Summary
Vulnerability in Froxlor (CVE-2026-100718). 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 does not enforce the mail.allow_external_domains policy in the EmailSender.add API command. When an administrator has enabled the allowed-sender feature but disabled external allowed-sender domains (mail.enable_allow_sender = 1, mail.allow_external_domains = 0), an authenticated customer with API access can still use EmailSender.add to register an arbitrary external sender address for their mailbox, which is stored despite the policy. This creates a bypass between the UI/administrator configuration and the API, and — where the generated mail configuration consumes the allowed-sender table — allows a customer to authorize sender identities outside their hosted domains, facilitating sender spoofing. 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-100718 has been found in Froxlor.
Data can be tampered with by attackers. CVSS score: 7.1/10.
What to do: upgrade Froxlor to 2.3.12 or later.
If unsure, ask your IT team or search "Froxlor CVE-2026-100718" on the vendor's site.
CVE-2026-100718 (Froxlor) — CWE-276 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
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.
A vulnerability (CWE-276) exists in Froxlor.
Check the vendor advisory for the affected versions of Froxlor.
Severity: High (CVSS 7.1/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