Description
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.
Published: 2026-09-26
Score: 7.1 High
EPSS: < 1% Very Low
KEV: No
Impact: Authentication Bypass
Action: Apply Patch
AI Analysis

Impact

Froxlor does not enforce the mail.allow_external_domains policy when an API call to EmailSender.add is made. Even when the administrator enables allowed-sender functionality but blocks external domains, an authenticated customer can register arbitrary external sender addresses for their mailbox. The stored addresses are then usable by the mail system, creating a secret channel that bypasses UI configuration and allows a customer to own sender identities outside the domains they host, thereby enabling spoofing of outbound mail.

Affected Systems

The affected vendor is Froxlor. All installations of Froxlor up through version 2.3.10 are vulnerable, and the issue is resolved in version 2.3.12. The vulnerability applies to any deployment that has the allowed-sender feature enabled while disallowing external domains.

Risk and Exploitability

The CVSS rating of 7.1 reflects a moderate‑to‑high impact for authenticated users. Because the attack requires a valid API credential, the likelihood of exploitation is limited to legitimate API users or compromised accounts, but it remains feasible without additional privileges. The EPSS is not available, and the vulnerability is not reported in CISA’s KEV catalog. Attackers can abuse the API to register external addresses, resulting in malicious spam or phishing that appears to come from legitimate customer domains. The risk is mitigated by applying the vendor’s patch or disabling the external‑sender allowance so no such addresses can be recorded.

Generated by OpenCVE AI on September 26, 2026 at 15:59 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Froxlor to version 2.3.12 or later.
  • Disable the external‑sender allowance by setting mail.allow_external_domains to 0 and, if possible, mail.enable_allow_sender to 0 to prevent any external address registration.
  • Restrict API access for EmailSender.add to administrative users only, ensuring that only authorized personnel can add sender addresses.

Generated by OpenCVE AI on September 26, 2026 at 15:59 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sun, 27 Sep 2026 00:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Sat, 26 Sep 2026 13:30:00 +0000

Type Values Removed Values Added
Description 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.
Title Froxlor before 2.3.12 Authentication Bypass via EmailSender.add
First Time appeared Froxlor
Froxlor froxlor
Weaknesses CWE-276
CPEs cpe:2.3:a:froxlor:froxlor:*:*:*:*:*:*:*:*
Vendors & Products Froxlor
Froxlor froxlor
References
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N'}

cvssV4_0

{'score': 7.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-09-26T23:07:02.407Z

Reserved: 2026-09-26T02:40:56.225Z

Link: CVE-2026-100718

cve-icon Vulnrichment

Updated: 2026-09-26T23:06:59.221Z

cve-icon NVD

Status : Deferred

Published: 2026-09-26T14:16:57.917

Modified: 2026-09-26T23:16:33.417

Link: CVE-2026-100718

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-26T16:30:07Z

Weaknesses
  • CWE-276

    Incorrect Default Permissions