DNS record manipulation via unfiltered newlines
Published Apr 23, 2026 · Updated Apr 23, 2026
DNS zone file injection in Froxlor before 2.3.6 allows remote authenticated users to alter DNS records through the DomainZones.add API. DomainZones.add accepts unlisted record types and preserves embedded newlines, which DnsEntry.__toString writes directly into a BIND zone file. Customer credentials and DNS-editing access are required; injected records can redirect traffic or alter mail policy, while malformed directives can prevent the affected zone from loading.
Summary
What happened
DNS zone file injection in Froxlor before 2.3.6 allows remote authenticated users to alter DNS records through the DomainZones.add API. DomainZones.add accepts unlisted record types and preserves embedded newlines, which DnsEntry.__toString writes directly into a BIND zone file. Customer credentials and DNS-editing access are required; injected records can redirect traffic or alter mail policy, while malformed directives can prevent the affected zone from loading.
The record
- CVE
- CVE-2026-41230
- Published
- Apr 23, 2026
- Updated
- Apr 23, 2026
- Vendor
- Froxlor
- Product
- Froxlor
- Classifications
- CWE-93, CAPEC-81, CAPEC-15, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 23, 2026CVE publishedPublication date reported by the CVE source.
- Apr 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.3.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-47hf-23pw-3m8c API proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo