Answer in brief
CVE-2026-100718 records a High severity (CVSS 7.1) vulnerability in Froxlor before 2.3.12 Authentication Bypass via EmailSender.add. The current sources do not mark it as known exploited. The current feed maps froxlor/froxlor (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps froxlor/froxlor (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| froxlor/froxlorgeneric | >=0 <2.3.12 | 2.3.12 |
Published upstream
Sep 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 26, 2026
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.
Quoted source text, attributed separately from HOL analysis.