CVE-2026-41230
Froxlor is open source server administration software. Prior to …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/froxlor/froxlor/commit/47a8af5d9523cb6ec94567405cfc2e294d3a1442
- github.com/froxlor/froxlor/releases/tag/2.3.6
- github.com/froxlor/froxlor/security/advisories/GHSA-47hf-23pw-3m8c
- nvd.nist.gov/vuln/detail/CVE-2026-41230
- github.com/advisories/GHSA-47hf-23pw-3m8c
- nvd.nist.gov/vuln/detail/CVE-2026-41230
- cve.org/CVERecord?id=CVE-2026-41230
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.