{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-100710 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-100710 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-100710 is a medium-severity vulnerability in froxlor, published on 26 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-100710 and fix it if it is affected.\n\nWhat it is: CVE-2026-100710 is a medium-severity vulnerability in froxlor, published on 26 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-100710 in the wild and no public exploit code.\n\nAffected product: froxlor. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-100710/ (Markdown: https://insights.sbomify.com/CVE-2026-100710/index.md)","id":"CVE-2026-100710","markdown":"https://insights.sbomify.com/CVE-2026-100710/index.md","name":"CVE-2026-100710","record":{"aliases":["GHSA-6v5g-8vmm-8pqh","GHSA-79gx-h528-j9xf"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Froxlor hosting panel","requires_auth":"high_privilege","summary":"Authenticated users with specific permissions can read DKIM private keys via API, enabling email spoofing and DMARC bypass.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Froxlor before 2.3.12 DKIM Private Key Disclosure via API","id":"CVE-2026-100710","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"froxlor before 2.3.12 Authentication Bypass via Session Persistence","id":"CVE-2026-100711"},"packages":[],"prev":{"headline":"Froxlor before 2.3.11 2FA Bypass via Namespace Confusion","id":"CVE-2026-100709"},"products":["froxlor"],"published":"2026-09-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-26","vendors":["froxlor"]},"summary":"Authenticated users with specific permissions can read DKIM private keys via API, enabling email spoofing and DMARC bypass.","url":"https://insights.sbomify.com/CVE-2026-100710/"}