dbcve.org
IpfireApplication

CVE-2025-34317

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-28
Fix available
A fix is available. Upgrade to after 2.29 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
IPFire versions prior to 2.29 (Core Update 198) contain a stored cross-site scripting (XSS) vulnerability that allows an authenticated attacker to inject arbitrary JavaScript code through the TLS_HOSTNAME parameter when adding a new DNS entry. When a user adds a DNS entry, the application issues an HTTP POST request to /cgi-bin/dns.cgi and the TLS hostname is provided in the TLS_HOSTNAME parameter. The value of this parameter is stored and later rendered in the web interface without proper sanitation or encoding, allowing injected scripts to execute in the context of other users who view the affected DNS configuration.

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

IPFire versions prior to 2.29 (Core Update 198) contain a stored XSS vulnerability in the DNS management interface. The TLS_HOSTNAME parameter in /cgi-bin/dns.cgi accepts unsanitized input that is stored and later rendered in the web interface without proper encoding, allowing authenticated attackers to inject arbitrary JavaScript that executes in the browsers of other users viewing DNS configuration.

MitigationUpgrade to IPFire 2.29 (Core Update 198) or later which includes proper input sanitization and output encoding for the TLS_HOSTNAME parameter.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
IpfireApplication
Affected:<= 2.29= 2.29

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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. Identify if IPFire is installed
    Check for IPFire configuration directories: ls -la /var/ipfire/ or /etc/ipfire/. Alternatively, check the web interface is accessible at /cgi-bin/dns.cgi
    Affected if The /var/ipfire or /etc/ipfire directory exists, indicating IPFire is present
  2. Determine the IPFire version
    Check the version file: cat /var/ipfire/version or look for /etc/ipfire/version. This file contains the Core Update version number
    Affected if Version is 2.29 or lower (Core Update 198 or lower)
  3. Check if DNS with TLS is configured
    Examine the DNS proxy configuration: cat /var/ipfire/dns/config or similar file under /var/ipfire/dns/. Look for entries related to TLS_HOSTNAME or DNS-over-TLS settings
    Affected if DNS proxy is enabled with TLS/DoT configured and TLS_HOSTNAME parameter is present in the configuration
  4. Inspect the TLS_HOSTNAME parameter value
    In the DNS configuration file (e.g., /var/ipfire/dns/config), locate the TLS_HOSTNAME field and examine its stored value for suspicious characters like <script>, javascript:, onerror=, or other HTML/JavaScript tags
    Affected if The TLS_HOSTNAME value contains unsanitized input with script tags or event handlers (e.g., <script>, onload=, onerror=) indicating exploitation has occurred

A user is affected if they are running IPFire version 2.29 or lower with DNS-over-TLS enabled, and the TLS_HOSTNAME configuration contains malicious JavaScript payloads indicating the XSS vulnerability has been exploited.

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
Upgrade available Upgrade to a release after 2.29
Interim mitigation

Upgrade to IPFire 2.29 (Core Update 198) or later which includes proper input sanitization and output encoding for the TLS_HOSTNAME parameter.

Recommended fix High confidence

IPFire 2.29 Core Update 198 or later

  1. Access the IPFire web administration interface
  2. Navigate to System > Updates or check for available updates
  3. Upgrade to IPFire 2.29 Core Update 198 or later to obtain the fix for this stored XSS vulnerability
  4. After upgrading, verify the DNS settings page no longer reflects unsanitized input

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

Fix this in Ipfire Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34317 — 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-2025-34317 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