Vulnerability in froxlor/froxlor (CVE-2026-41234)
Summary
Vulnerability in froxlor/froxlor (CVE-2026-41234). Data can be tampered with by attackers. Exploitable via DomainZones.add. Mitigation: upgrade to 2.3.7 or later.
Original description
The description as published by the source.
Froxlor is open source server administration software. Prior to version 2.3.7, the DomainZones.add API endpoint does not sanitize newline characters in TXT record content. An authenticated customer with DNS editing enabled can inject newlines into TXT record values, which break out of the record line in the generated BIND zone file. This enables injection of arbitrary BIND directives ($INCLUDE, $GENERATE) and arbitrary DNS records (A, MX, CNAME) into the zone file written to disk by the DNS rebuild cron. This is an incomplete fix for CVE-2026-30932 (GHSA-x6w6-2xwp-3jh6), which patched the same newline injection for LOC, RP, SSHFP, and TLSA record types but did not patch TXT records. Version 2.3.7 contains an updated patch.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-41234 has been found in froxlor/froxlor.
Attackers can target a specific entry point like DomainZones.add over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.6/10.
What to do: upgrade froxlor/froxlor to 2.3.7 or later.
If unsure, ask your IT team or search "froxlor/froxlor CVE-2026-41234" on the vendor's site.
CVE-2026-41234 (froxlor/froxlor) — CWE-74 / CVSS v3 7.6
Attack vector: remote (network-reachable) / no user interaction
Attack surface: DomainZones.add / DomainZones.php / PHP_EOL / dns_content
Patched: 2.3.7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-74) exists in froxlor/froxlor. Attackers reach the vulnerable code path via DomainZones.add.
Check the vendor advisory for the affected versions of froxlor/froxlor. Attack surface: DomainZones.add / DomainZones.php / PHP_EOL / dns_content.
Severity: High (CVSS 7.6/10). Data can be tampered with by attackers.
Update to 2.3.7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'froxlor/froxlor' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'froxlor/froxlor' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
froxlor/froxlorを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade froxlor/froxlor to 2.3.7ステージング環境で 2.3.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com