Vulnerability · Published Sep 26, 2026 · Assigned by VulnCheck

CVE-2026-100708Froxlor before 2.3.13 Private Key Disclosure via Certificates API

High 7.1

In plain English

A high-severity information exposure in froxlor from froxlor. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 5% of all known vulnerabilities).

Severity (CVSS 3.1)7.1High

Exploit odds (30 days)0.2%top 94.9% of all CVEs

Exploited in the wildNo reportsCISA SSVC: poc

Attack toolingNoneno public tooling known

Official 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.

Affected products (as reported)

Vendor	Product	Versions
froxlor	froxlor	0 – before 2.3.13

Weakness: CWE-200 · Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

References

GitHub Security Advisory (GHSA-6q2v-jjq5-m2c8) vendor-advisory
VulnCheck Advisory: Froxlor before 2.3.13 Private Key Disclosure via Certificates API third-party-advisory