Vulnerability in froxlor/froxlor (CVE-2026-30932)
Summary
Vulnerability in froxlor/froxlor (CVE-2026-30932). Successful exploitation can lead to full system takeover. Exploitable via DomainZones.add. Mitigation: upgrade to 2.3.5 or later.
Original description
The description as published by the source.
Summary
The DomainZones.add API endpoint (accessible to customers with DNS enabled) does not validate the content field for several DNS record types (LOC, RP, SSHFP, TLSA). An attacker can inject newlines and BIND zone file directives (e.g. $INCLUDE) into the zone file that gets written to disk when the DNS rebuild cron job runs.
Affected Code
lib/Froxlor/Api/Commands/DomainZones.php, lines 213-214, 253-254, 290-291, 292-293:
} elseif ($type == 'LOC' && !empty($content)) {
$content = $content; // no validation
} ...
} elseif ($type == 'RP' && !empty($content)) {
$content = $content; // no validation
} ...
} elseif ($type == 'SSHFP' && !empty($content)) {
$content = $content; // no validation
} elseif ($type == 'TLSA' && !empty($content)) {
$content = $content; // no validation
}
There is even a TODO comment at line 148 acknowledging this gap:
// TODO regex validate content for invalid characters
The content is then written directly into the BIND zone file via DnsEntry::__toString() (line 83 of lib/Froxlor/Dns/DnsEntry.php):
return $this->record . "\t" . $this->ttl . "\t" . $this->class . "\t" . $this->type . "\t" ... . $_content . PHP_EOL;
And the zone file is written to disk in lib/Froxlor/Cron/Dns/Bind.php line 121:
fwrite($zonefile_handler, $zoneContent . $subzones);
PoC
As a customer with DNS management enabled and an API key, add a LOC record with injected BIND directives:
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-30932 has been found in froxlor/froxlor.
Attackers can target a specific entry point like DomainZones.add over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade froxlor/froxlor to 2.3.5 or later.
If unsure, ask your IT team or search "froxlor/froxlor CVE-2026-30932" on the vendor's site.
CVE-2026-30932 (froxlor/froxlor) — CWE-74
Attack vector: remote (network-reachable) / no user interaction
Attack surface: DomainZones.add / content / dns_content / dns_type
Patched: 2.3.5 — 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 / content / dns_content / dns_type.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 2.3.5.
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.5ステージング環境で 2.3.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com