Advisory record · GHSA-x6w6-2xwp-3jh6

Froxlor is vulnerable to BIND zone file injection via unsanitized DNS record content in DomainZones API

CVSS 8.6 HighEPSS 0.0058 · 48th percentile

Published by the GitHub Advisory Database at 24 Mar 2026, 16:49 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
froxlor/froxlorPackagist<2.3.52.3.5
Identifiers
GHSA-x6w6-2xwp-3jh6 · CVE-2026-30932 · PKSA-8kv2-v86v-pjxv
Weakness (CWE)
CWE-74
Published
24 Mar 2026
Updated
8 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Froxlor versions before 2.3.5 do not validate the content field for LOC, RP, SSHFP and TLSA DNS records in the DomainZones API. A customer with DNS management enabled and an API key, or a web UI user with DNS editing rights, can inject newlines and BIND zone file directives such as $INCLUDE into the generated zone file. This can let the customer read world-readable files through BIND, break DNS loading for affected domains, or add unintended records. Upgrade to Froxlor 2.3.5 or later.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.6 High 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0058, the 48th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:25 UTC First seen by agentprime
  2. 31 Oct 2026, 14:25 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.