dbcve.org
InjectionWeakness · CWE-74

CVE-2026-41234

HIGH · 7.6 CVSS v3.1 Published 2026-06-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Froxlor's DomainZones.add API endpoint fails to sanitize newline characters in TXT record content, allowing authenticated customers with DNS editing permissions to inject newlines that break out of the TXT record line in generated BIND zone files. This enables injection of arbitrary BIND directives ($INCLUDE, $GENERATE) and DNS records (A, MX, CNAME) into the zone file. This is an incomplete fix from CVE-2026-30932 which patched LOC, RP, SSHFP, and TLSA but not TXT records.

MitigationUpgrade to Froxlor version 2.3.7 or later which contains the complete patch for newline injection across all record types including TXT records.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Froxlor is installed
    Look for Froxlor installation directory (commonly /var/www/html/froxlor or /usr/share/froxlor) or check for froxlor package via package manager (dpkg -l | grep froxlor, rpm -qa | grep froxlor)
    Affected if Froxlor is installed on the system
  2. Identify installed Froxlor version
    Check version file typically located at include/version.php or VERSION file in Froxlor root directory, or check admin panel footer for version number
    Affected if Version is lower than 2.3.7 (e.g., 2.3.6, 2.3.5, etc.)
  3. Verify DomainZones.add API endpoint exists
    Locate API routing configuration (usually in lib/API/ or api/ directory) and check for DomainZones.add or DomainZones::add method handling
    Affected if API endpoint exists and is accessible without additional authentication beyond basic user login
  4. Check if DNS zone management is enabled
    Examine Froxlor configuration for enabled modules (typically in settings like dnsenabled, or check if DNS module is activated in the admin panel under System > Settings > DNS)
    Affected if DNS module is enabled and users have access to create/edit TXT records
  5. Inspect BIND zone files for injected content
    Check generated zone files in /etc/bind/, /var/lib/bind/, or Froxlor's zone file output directory for unexpected $INCLUDE, $GENERATE directives or additional A, MX, CNAME records not created through normal Froxlor interface
    Affected if Zone files contain unexpected records or directives with malformed TXT record content preceding them

User is affected if running Froxlor version lower than 2.3.7 with DNS module enabled and the DomainZones.add API accessible to users with DNS editing privileges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Froxlor version 2.3.7 or later which contains the complete patch for newline injection across all record types including TXT records.

Recommended fix High confidence

Froxlor version 2.3.7

  1. 1. Identify the currently installed Froxlor version by checking the version file or admin interface.
  2. 2. Backup the Froxlor installation directory and database before proceeding with the upgrade.
  3. 3. Download Froxlor version 2.3.7 from the official repository or source.
  4. 4. Extract and install the new version, overwriting existing files while preserving configuration.
  5. 5. Run any provided database migration scripts included in the 2.3.7 release.
  6. 6. Clear any caches and verify the DNS rebuild cron functions correctly.
  7. 7. Test that TXT record creation via the DomainZones.add API endpoint properly sanitizes newline characters.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41234 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41234 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data