Read the docs
TI-2026-64874 Aliases CVE-2026-100718GHSA-m5mc-84wm-h4mw

Froxlor before 2.3.12 Authentication Bypass via EmailSender.add

Priority LOW 30CWE-276Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
—
Confidentiality · integrity · availability
Low · High · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00186 8th percentileScored 2026-11-07
Fix Fixed froxlor (froxlor): 2.3.12

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
froxlorfroxlorbefore 2.3.122.3.12Patch availableCNA
  • froxlor Vendorfroxlor Affected before 2.3.12 Fixed in 2.3.12 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:froxlor:froxlor:*:*:*:*:*:*:*:*——froxlor
  • cpe:2.3:a:froxlor:froxlor:*:*:*:*:*:*:*:* Versions — — ·froxlor

Remediation

  • Fix · CNA froxlor (froxlor) Fixed in 2.3.12

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    froxlor 2.3.12

    11 records Highest priority Priority HIGH 3 HIGH, 3 MEDIUM, 5 LOW

    Other records, highest priority first

    • TI-2026-64867 froxlor before 2.3.12 Authentication Bypass via Session PersistencePriority HIGH 77
    • TI-2026-64872 Froxlor before 2.3.12 Privilege Escalation via SymlinkPriority HIGH 76
    • TI-2026-64871 Froxlor before 2.3.12 Arbitrary File Deletion via SymlinkPriority HIGH 72
    Show all 11 records →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-100718
  2. 2026-10-03 Alias added: GHSA-m5mc-84wm-h4mw

References

Advisory 1

  • TI-2023-00300 Command Injection in froxlor/froxlor CVSS 3.1HIGH 8.8
  • TI-2023-02973 Improper Restriction of Excessive Authentication Attempts in froxlor/froxlor CVSS 3.1CRITICAL 9.8
  • TI-2023-01234 Authentication Bypass by Primary Weakness in froxlor/froxlor CVSS 3.1CRITICAL 9.8
  • TI-2023-01911 Unrestricted Upload of File with Dangerous Type in froxlor/froxlor CVSS 3.1HIGH 8.8
  • TI-2026-64867 froxlor before 2.3.12 Authentication Bypass via Session Persistence CVSS 4.0HIGH 8.7
  • TI-2026-76945 Symlink following in Froxlor enables root privilege escalation CVSS 4.0CRITICAL 9.4
See all 86 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences