Servers and applications
CVE-2026-41230
BIND Zone File Injection via Unsanitized DNS Record Content in DomainZones::add()
- Severity
- High 8.5
- Published
- 15 Apr 2026
- Last changed
- 11 Nov 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 2.3.6
- Exploit chance
- 0.3% in the next 30 daysHigher than 28% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- CRLF injection (CWE-93)
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Change data · Slow it down
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L- Also known as
- GHSA-47hf-23pw-3m8c
- Sources
- NVD, Project advisories (GitHub)
Description
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.
The type parameter is accepted directly from user input with no validation against allowed values:
The if/elseif chain at lines 170-317 validates content only for 13 known types: A, AAAA, CAA, CNAME, DNAME, LOC, MX, NS, RP, SRV, SSHFP, TLSA, TXT. Any type not in this list falls through with no content validation at all. There is a TODO comment at line 148 acknowledging missing validation:
Affected software
| Software | Affected versions |
|---|---|
FroxlorServers and applications · cpe:a:froxlor:froxlor |
|
FroxlorServers and applications · github:froxlor/froxlor |
|
About Froxlor
The server administration software for your needs - The official Froxlor development Git repository
- Monthly downloads (Packagist)
- 159Packagist, 15 Nov 2026
- Total downloads (Packagist)
- 406Packagist, 15 Nov 2026
- GitHub stars
- 1,752GitHub, 15 Nov 2026
- Forks
- 467GitHub, 15 Nov 2026
- Latest release
- 2.3.17GitHub, 15 Nov 2026
- Released
- 8 Nov 2026GitHub
- License
- GNU Lesser General Public License, version 2.1Wikidata
- Written in
- PHPWikidata
- First published on GitHub
- 6 Mar 2012GitHub
Vulnerabilities in Froxlor
- In our list
- 97
- Published in the last 12 months
- 56
- Critical, last 12 months
- 6
- High, last 12 months
- 24
- Known exploited
- 0
- CVE-2026-130755Froxlor before 2.3.16 Authorization Bypass via Traffic.listing API CommandMedium 5.3 18 Nov 2026
- CVE-2026-121436Froxlor 2.3.8 before 2.3.15 API Key Disclosure via api_keys.phpHigh 8.6 3 Nov 2026
- CVE-2026-121435Froxlor before 2.3.15 Authorization Bypass via Mysqls.add APIMedium 5.3 3 Nov 2026
- CVE-2026-121434Froxlor 2.3.0 before 2.3.15 Authorization Bypass via Certificates.update APIMedium 5.3 3 Nov 2026
- GHSA-vhfr-xvmw-p2m9Froxlor customer Traffic listing API bypasses the customer_hide_options traffic restrictionMedium 4.3 3 Nov 2026
- CVE-2026-113678Froxlor before 2.3.15 Symlink Following Privilege Escalation via Traffic CronCritical 9.4 20 Oct 2026
References
- NVD https://nvd.nist.gov/vuln/detail/CVE-2026-41230
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-41230
- GitHub Advisory Database https://github.com/advisories/GHSA-47hf-23pw-3m8c
- github.com https://github.com/froxlor/froxlor/security/advisories/GHSA-47hf-23pw-3m8c