{
  "id": "CVE-2026-100718",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-100718",
  "published_at": "2026-09-26T13:24:09.189Z",
  "title": "Froxlor before 2.3.12 Authentication Bypass via EmailSender.add",
  "vendor": "froxlor",
  "product": "froxlor",
  "cvss": {
    "score": 7.1,
    "source": "cna",
    "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"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "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.",
  "cwe": "CWE-276",
  "cvss_by_source": {
    "cna": 7.1
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "froxlor",
        "product": "froxlor",
        "ranges": [
          "\u003c 2.3.12"
        ],
        "fixed_in": [
          "2.3.12"
        ]
      }
    ],
    "upgrade": [
      "Upgrade froxlor to 2.3.12 or later."
    ],
    "references": [
      {
        "kind": "Vendor advisory",
        "url": "https://github.com/froxlor/froxlor/security/advisories/GHSA-m9j6-9856-68xf"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
