PoC Monitor
← All CVEs
CVE-2026-100708published 26 Sep 2026 13:24 UTCData: JSON · API

Froxlor

Froxlor before 2.3.13 Private Key Disclosure via Certificates API

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.1high · scored by CNA · CWE-200
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

froxlor froxlor
  • < 2.3.13

Fixed in 2.3.13

Mitigation

Upgrade froxlor to 2.3.13 or later.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published26 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.