Skip to main content

Froxlor CVE-2026-100710

| EUVDEUVD-2026-87683 MEDIUM
Information Exposure (CWE-200)
2026-09-26 VulnCheck GHSA-6v5g-8vmm-8pqh
6.9
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as delegated admin with customers_see_all
  2. Delivery
    Call Domains.listing/SubDomains API
  3. Exploit
    Receive wildcard rows incl dkim_privkey
  4. Execution
    Harvest cross-tenant DKIM keys
  5. Impact
    Sign spoofed email passing DKIM/DMARC

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK

2 techniques across 2 tactics: Collection, Discovery

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires an authenticated Froxlor admin account that is NOT superadmin but holds the delegated customers_see_all flag; exploitation is via the authenticated API methods Domains.get, Domains.listing, SubDomains.get, or the admin branch of SubDomains.listing, which perform an unfiltered wildcard SELECT over panel_domains and return dkim_privkey. Limiting factors: high privilege is required (delegated multi-admin/reseller-style access), so single-tenant or superadmin-only deployments are not exposed cross-tenant; the flaw only matters in multi-tenant configurations where customers_see_all has been granted to a partially-trusted admin. No user interaction and no non-standard configuration beyond that privilege grant are needed.

Impact

This is a real but bounded risk. The vendor CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:H/UI:N/VC:H, all other impacts N) is internally consistent with the description: a confidentiality-only disclosure requiring an authenticated, high-privilege actor (a non-superadmin admin holding the delegated customers_see_all flag). PR:H is the dominant limiting factor - this is not remotely exploitable by an anonymous attacker, so it will not see mass automated exploitation. There is no EPSS score, no CISA KEV listing, and no public exploit code, so exploitation status is 'no public exploit identified at time of analysis'; these signals are consistent (low-probability, no active exploitation) rather than conflicting. The impact, however, is qualitatively serious: leaked DKIM private keys enable durable email spoofing that passes DKIM/DMARC for other tenants' domains, and a single listing call dumps every visible domain's key. Net: a genuine cross-tenant confidentiality flaw that multi-tenant hosting providers should patch promptly, but not an emergency-patch-tonight, mass-scanned issue given the PR:H gate. Note the value lies in trust/integrity of downstream email even though CVSS scores it purely as confidentiality.

Exploit ScenarioDerived

A hosting provider grants a reseller or junior admin the customers_see_all flag without full superadmin rights. That admin calls Domains.listing (or SubDomains.listing) via the API, receiving the raw panel_domains rows including dkim_privkey for every visible domain across other tenants, then uses the harvested private keys to sign phishing email that passes DKIM verification and DMARC alignment for those domains. No public exploit code is known, and exploitation requires the authenticated delegated-admin privilege.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 26, 2026

Froxlor through 2.3.10 exposes DKIM private signing keys through its customer-facing API: the Domains.get, Domains.listing, SubDomains.get, and admin SubDomains.listing methods run an unfiltered wildcard SELECT over the panel_domains table and return the dkim_privkey column verbatim to the caller. An authenticated admin who is not a superadmin but has been granted the delegated customers_see_all flag can retrieve the DKIM private keys of every domain visible to them across tenants, and a single listing call discloses the keys for all such domains. Compromising those keys lets the holder forge DKIM signatures that pass DKIM verification and DMARC alignment for the affected domains; the issue is a follow-on to an earlier incomplete fix that scrubbed password and data_2fa but left dkim_privkey in the response. There is no public exploit identified at time of analysis, and the risk is real but bounded because it requires a high-privilege delegated admin role in a multi-tenant deployment; the vendor has released the fix in 2.3.12.

RemediationAI

Upgrade Froxlor to 2.3.12, the vendor-released patch that completes the earlier filtering change by excluding dkim_privkey from the API responses, as documented in the advisory at https://github.com/froxlor/froxlor/security/advisories/GHSA-79gx-h528-j9xf and https://www.vulncheck.com/advisories/froxlor-before-2.3.12-dkim-private-key-disclosure-via-api. If upgrading immediately is not possible, audit and revoke the delegated customers_see_all flag from any admin account that is not a trusted superadmin, restricting the affected Domains and SubDomains API methods to fully trusted operators - the trade-off is that legitimate reseller or multi-customer workflows lose cross-tenant visibility, but the unsafe key exposure path is closed. Because DKIM private keys may already have been read before patching, treat them as compromised: rotate the DKIM key pairs for all domains on affected installs and republish the corresponding public keys in DNS, accepting that mail flow may be briefly unaligned while DNS propagates. Rotating keys alone ensures forged signatures made with the old key no longer validate, and combined with the 2.3.12 upgrade it fully removes both the disclosure vector and any residual ability to sign mail as the affected domains.

Affected VersionsENISA

Froxlor 0 <2.3.12

Affected Packages

euvd froxlor fix: 2.3.12

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Froxlor is an open-source server management panel used for shared and multi-tenant hosting, where each customer's mail domains are backed by rows in the panel_domains table, including the DKIM private key stored in the dkim_privkey column. Under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), four API surfaces - Domains::get(), Domains::listing(), SubDomains::get(), and the admin branch of SubDomains::listing() - perform a SELECT * against panel_domains and serialize the full row back to the caller without stripping sensitive columns. An earlier hardening pass removed password and data_2fa fields from these responses but overlooked dkim_privkey, so the incomplete fix left the DKIM private key readable. DKIM signing keys are cryptographically sensitive because possession of the private key allows arbitrary message signing that validates against the domain's published DNS public key, directly enabling DMARC-aligned spoofing. The affected CPE is cpe:2.3:a:froxlor:froxlor:*:*:*:*:*:*:*:* for versions below 2.3.12; the disclosure is authorization-bound rather than anonymous, and the CVSS v4.0 vector reports PR:H (high privileges required), VC:H (high confidentiality impact), and no integrity or availability impact on the vulnerable component.

Know when Froxlor gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 6.9 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
vuln.today AI 6.8 MEDIUM

Authenticated delegated admin (PR:H) over network API with no interaction; scope changes as one tenant's admin reads another tenant's secrets (S:C); confidentiality-only, no direct integrity/availability impact.

3.1 AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
High
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

1
Patch available
Sep 26, 2026 - 14:02 EUVD

DescriptionCVE.org

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.

Threat Intelligence Overview

EPSS Score
0.2%
Top 86% exploitable
Prevalence
Low
niche open-source web-hosting control panel, limited enterprise footprint
Data Quality
4 sources
Confidence: Medium
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

34
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

CVE-2023-0315 HIGH POC
8.8 Jan 16

Command Injection in GitHub repository froxlor/froxlor prior to 2.0.8. Rated high severity (CVSS 8.8), this vulnerabilit

CVE-2023-3173 CRITICAL POC
9.8 Jun 09

Improper Restriction of Excessive Authentication Attempts in GitHub repository froxlor/froxlor prior to 2.0.20. Rated cr

CVE-2023-1307 CRITICAL POC
9.8 Mar 10

Authentication Bypass by Primary Weakness in GitHub repository froxlor/froxlor prior to 2.0.13. Rated critical severity

CVE-2021-42325 CRITICAL POC
9.8 Oct 12

Froxlor through 0.10.29.1 allows SQL injection in Database/Manager/DbManagerMySQL.php via a custom DB name. Rated critic

CVE-2026-26279 CRITICAL POC
9.1 Mar 03

Command injection in Froxlor server admin before 2.3.4 due to typo (== instead of =) disabling input validation entirely

CVE-2023-6069 HIGH POC
8.8 Nov 10

Improper Link Resolution Before File Access in GitHub repository froxlor/froxlor prior to 2.1.0. Rated high severity (CV

CVE-2023-2034 HIGH POC
8.8 Apr 14

Unrestricted Upload of File with Dangerous Type in GitHub repository froxlor/froxlor prior to 2.0.14. Rated high severit

CVE-2023-1033 HIGH POC
8.8 Feb 25

Cross-Site Request Forgery (CSRF) in GitHub repository froxlor/froxlor prior to 2.0.11. Rated high severity (CVSS 8.8),

CVE-2023-0877 HIGH POC
8.8 Feb 17

Code Injection in GitHub repository froxlor/froxlor prior to 2.0.11. Rated high severity (CVSS 8.8), this vulnerability

CVE-2023-0671 HIGH POC
8.8 Feb 04

Code Injection in GitHub repository froxlor/froxlor prior to 2.0.10. Rated high severity (CVSS 8.8), this vulnerability

CVE-2020-10235 HIGH POC
8.8 Mar 09

An issue was discovered in Froxlor before 0.10.14. Rated high severity (CVSS 8.8), this vulnerability is remotely exploi

CVE-2023-50256 HIGH POC
7.5 Jan 03

Froxlor is open source server administration software. Rated high severity (CVSS 7.5), this vulnerability is remotely ex

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy