Vulnerability Description
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.
CVSS Score
MEDIUM
Related Weaknesses (CWE)
References
- https://github.com/froxlor/froxlor/security/advisories/GHSA-79gx-h528-j9xf
- https://www.vulncheck.com/advisories/froxlor-before-2.3.12-dkim-private-key-disc
FAQ
What is CVE-2026-100710?
CVE-2026-100710 is a vulnerability with a CVSS score of 4.9 (MEDIUM). 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 SEL...
How severe is CVE-2026-100710?
CVE-2026-100710 has been rated MEDIUM with a CVSS base score of 4.9/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-100710?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.