# Froxlor is vulnerable to BIND zone file injection via unsanitized DNS record content in DomainZones API

Advisory record · `GHSA-x6w6-2xwp-3jh6`

- **Identifiers:** `GHSA-x6w6-2xwp-3jh6` · `CVE-2026-30932` · `PKSA-8kv2-v86v-pjxv`
- **State:** Confirmed
- **Severity:** CVSS 8.6 High
- **Critical:** No
- **Weakness (CWE):** [CWE-74](https://cwe.mitre.org/data/definitions/74.html)
- **Tags:** [Other injection](https://agentprime.io/advisories/tag/injection.md)
- **Published:** 24 Mar 2026
- **Updated:** 8 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 24 Mar 2026, 16:49 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `froxlor/froxlor` (Packagist): affected `<2.3.5`; fixed in `2.3.5`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Froxlor versions before 2.3.5 do not validate the content field for LOC, RP, SSHFP and TLSA DNS records in the DomainZones API. A customer with DNS management enabled and an API key, or a web UI user with DNS editing rights, can inject newlines and BIND zone file directives such as $INCLUDE into the generated zone file. This can let the customer read world-readable files through BIND, break DNS loading for affected domains, or add unintended records. Upgrade to Froxlor 2.3.5 or later.

Written 3 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.6 High, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0058, the 48th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:25 UTC: First seen by agentprime
- 31 Oct 2026, 14:25 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-x6w6-2xwp-3jh6)

## Sources

- [GitHub Advisory Database: GHSA-x6w6-2xwp-3jh6](https://github.com/advisories/GHSA-x6w6-2xwp-3jh6)
- [OSV: GHSA-x6w6-2xwp-3jh6](https://osv.dev/vulnerability/GHSA-x6w6-2xwp-3jh6)
- <https://github.com/froxlor/froxlor/security/advisories/GHSA-x6w6-2xwp-3jh6>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-30932>
- <https://github.com/froxlor/froxlor/commit/b34829262dc32818b37f6a1eabb426d0b277a86b>
- <https://github.com/froxlor/froxlor>
- <https://github.com/froxlor/froxlor/releases/tag/2.3.5>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-x6w6-2xwp-3jh6>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-x6w6-2xwp-3jh6/>. Everything for agents: <https://agentprime.io/llms.txt>.