Froxlor through 2.3.10 does not filter sensitive columns from API responses: Domains::get(), Domains::listing(), SubDomains::get(), and the admin… (CVE-2026-100710)
Froxlor versions through 2.3.10 have an issue where sensitive columns, specifically the dkim_privkey field, are not filtered from API responses in certain domain-related API calls. This allows authenticated non-superadmin admins with the delegated customers_see_all flag to access DKIM private keys of other tenants' domains. The vulnerability enables unauthorized reading of private signing keys, which could be used to sign emails that pass DKIM verification and DMARC alignment. The issue was fixed in version 2.3.12.
AI Analysis
Technical Summary
Froxlor through version 2.3.10 does not properly filter sensitive columns from API responses in the Domains::get(), Domains::listing(), SubDomains::get(), and the admin branch of SubDomains::listing() methods. These methods perform a wildcard SELECT on the panel_domains table and return all columns unmodified, including the dkim_privkey field. An authenticated admin user with the delegated customers_see_all flag but without superadmin privileges can retrieve the DKIM private keys of domains belonging to other tenants. This vulnerability is a follow-up to a previous incomplete fix that removed password and data_2fa fields but not dkim_privkey. The vulnerability is resolved in Froxlor version 2.3.12.
Potential Impact
An attacker with authenticated admin access and the delegated customers_see_all flag can obtain DKIM private keys of other tenants' domains. This could allow the attacker to sign emails that appear legitimate by passing DKIM verification and DMARC alignment, potentially facilitating email spoofing or phishing attacks. The CVSS score is 4.9 (medium severity), reflecting the confidentiality impact without integrity or availability impact.
Mitigation Recommendations
Upgrade Froxlor to version 2.3.12 or later, where this vulnerability is fixed. No other mitigation is indicated by the vendor advisory. Since this is not a cloud service, remediation depends on applying the official patch.
Froxlor through 2.3.10 does not filter sensitive columns from API responses: Domains::get(), Domains::listing(), SubDomains::get(), and the admin… (CVE-2026-100710)
Description
Froxlor versions through 2.3.10 have an issue where sensitive columns, specifically the dkim_privkey field, are not filtered from API responses in certain domain-related API calls. This allows authenticated non-superadmin admins with the delegated customers_see_all flag to access DKIM private keys of other tenants' domains. The vulnerability enables unauthorized reading of private signing keys, which could be used to sign emails that pass DKIM verification and DMARC alignment. The issue was fixed in version 2.3.12.
CVSS v3.1
Score 4.9medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Froxlor through version 2.3.10 does not properly filter sensitive columns from API responses in the Domains::get(), Domains::listing(), SubDomains::get(), and the admin branch of SubDomains::listing() methods. These methods perform a wildcard SELECT on the panel_domains table and return all columns unmodified, including the dkim_privkey field. An authenticated admin user with the delegated customers_see_all flag but without superadmin privileges can retrieve the DKIM private keys of domains belonging to other tenants. This vulnerability is a follow-up to a previous incomplete fix that removed password and data_2fa fields but not dkim_privkey. The vulnerability is resolved in Froxlor version 2.3.12.
Potential Impact
An attacker with authenticated admin access and the delegated customers_see_all flag can obtain DKIM private keys of other tenants' domains. This could allow the attacker to sign emails that appear legitimate by passing DKIM verification and DMARC alignment, potentially facilitating email spoofing or phishing attacks. The CVSS score is 4.9 (medium severity), reflecting the confidentiality impact without integrity or availability impact.
Mitigation Recommendations
Upgrade Froxlor to version 2.3.12 or later, where this vulnerability is fixed. No other mitigation is indicated by the vendor advisory. Since this is not a cloud service, remediation depends on applying the official patch.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-6v5g-8vmm-8pqh
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-100710"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6ab89bd9f7a7c5410694201c
Added to database: 09/27/2026, 04:30:17 UTC
Last enriched: 09/27/2026, 04:41:13 UTC
Last updated: 09/28/2026, 01:47:40 UTC
Views: 17
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.