CVE-2026-41230

published 23 Apr 2026 · updated 11 Nov 2026

Froxlor has a BIND Zone File Injection via Unsanitized DNS Record Content in DomainZones::add()

9.5CriticalCVSS 8.5EPSS 0%1 public exploits

A public exploit exists; no exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 2.3.6.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
froxlorfroxlor<2.3.62.3.6
froxlor<2.3.6

Exploit evidence

1 public sources

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-41230 severity on Zeptric[![CVE-2026-41230](https://zeptric.io/badge/cve/CVE-2026-41230.svg)](https://zeptric.io/cve/CVE-2026-41230)