CVE-2026-41230: Froxlor has a BIND Zone File Injection via Unsanitized DNS Record Content in DomainZones::add()
Froxlor is open source server administration software. Prior to version 2.3.6, DomainZones::add() accepts arbitrary DNS record types without a whitelist and does not sanitize newline characters in the content field. When a DNS type not covered by the if/elseif validation chain is submitted (e.g., NAPTR, PTR, HINFO), content validation is entirely bypassed. Embedded newline characters in the content survive trim() processing, are stored in the database, and are written directly into BIND zone files via DnsEntry::toString(). An authenticated customer can inject arbitrary DNS records and BIND directives ($INCLUDE, $ORIGIN, $GENERATE) into their domain's zone file. Version 2.3.6 fixes the issue.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-41230?
CVE-2026-41230 is rated as a high severity vulnerability due to the potential for BIND Zone File Injection.
How do I fix CVE-2026-41230?
To fix CVE-2026-41230, upgrade Froxlor to version 2.3.6 or later where the vulnerability is patched.
What versions of Froxlor are affected by CVE-2026-41230?
Froxlor versions prior to 2.3.6 are affected by CVE-2026-41230.
What type of vulnerability is CVE-2026-41230?
CVE-2026-41230 is a BIND Zone File Injection vulnerability.
What impact does CVE-2026-41230 have on system security?
CVE-2026-41230 can allow an attacker to inject malicious DNS records, potentially leading to data loss or unauthorized access.