Vulnerability Description
Froxlor before 2.3.13 returns the ssl_key_file column — which stores the raw PEM TLS private-key content — verbatim in the JSON responses of the Certificates.get and Certificates.listing API commands, because the results of the underlying domain_ssl_settings queries are passed through ApiCommand::response() without any field stripping or allowlist. A low-privileged authenticated customer API caller can retrieve the private keys of their own domains' certificates, including Let's Encrypt keys that Froxlor generates server-side and stores root-only (0600) and to which the customer otherwise has no filesystem access; reseller and customers_see_all admin accounts can dump the private keys of other principals through the same sink. Disclosed keys enable domain impersonation, passive decryption of captured TLS traffic, and active machine-in-the-middle attacks.
CVSS Score
HIGH
Related Weaknesses (CWE)
References
- https://github.com/froxlor/froxlor/security/advisories/GHSA-6q2v-jjq5-m2c8
- https://www.vulncheck.com/advisories/froxlor-before-2.3.13-private-key-disclosur
- https://github.com/froxlor/froxlor/security/advisories/GHSA-6q2v-jjq5-m2c8
FAQ
What is CVE-2026-100708?
CVE-2026-100708 is a vulnerability with a CVSS score of 7.1 (HIGH). Froxlor before 2.3.13 returns the ssl_key_file column — which stores the raw PEM TLS private-key content — verbatim in the JSON responses of the Certificates.get and Certificates.listing API commands,...
How severe is CVE-2026-100708?
CVE-2026-100708 has been rated HIGH with a CVSS base score of 7.1/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-100708?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.