CVE-2026-100710

published 26 Sep 2026 · updated 26 Sep 2026

Froxlor before 2.3.12 DKIM Private Key Disclosure via API

4.9MediumCVSS 4.9EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 2.3.12.

Froxlor through 2.3.10 does not filter sensitive columns from API responses: Domains::get(), Domains::listing(), SubDomains::get(), and the admin branch of SubDomains::listing() perform a wildcard SELECT over the panel_domains table and return the row unmodified, including the panel_domains.dkim_privkey field. An authenticated, non-superadmin admin holding the delegated customers_see_all flag can therefore read the DKIM private signing keys of domains belonging to other tenants via Domains.get, Domains.listing, SubDomains.get, or SubDomains.listing, with a single listing call disclosing the key of every visible domain. The disclosed keys allow an attacker to sign email that passes DKIM verification and DMARC alignment for the affected domains. This is a follow-on to an incomplete fix that stripped password and data_2fa but not dkim_privkey. The issue is fixed in 2.3.12.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
froxlor<2.3.122.3.12

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-100710 severity on Zeptric[![CVE-2026-100710](https://zeptric.io/badge/cve/CVE-2026-100710.svg)](https://zeptric.io/cve/CVE-2026-100710)