CVE-2025-34309
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 · uneditedIPFire 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 SERVICE, LOGIN, and PASSWORD parameters when creating or editing a Dynamic DNS host. When a new Dynamic DNS host is added, the application issues an HTTP POST request to /cgi-bin/ddns.cgi and saves the values of the LOGIN, PASSWORD, and SERVICE parameters. The SERVICE value is displayed after the host entry is created, and the LOGIN and PASSWORD values are displayed when that host entry is edited. The values of these parameters are 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 or edit the affected Dynamic DNS entries.
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 confidenceIPFire versions before 2.29 (Core Update 198) contain a stored XSS vulnerability in the Dynamic DNS (ddns.cgi) component. Authenticated attackers can inject malicious JavaScript via SERVICE, LOGIN, and PASSWORD parameters when creating/editing Dynamic DNS hosts. These values are stored and later rendered in the web interface without sanitization or encoding, allowing script execution in the context of other users who view or edit these entries.
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< 2.29= 2.29CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine IPFire versionCheck the installed IPFire version via the web interface (System > Advance) or by inspecting /etc/system advancement. Compare the version number and Core Update build to the affected ranges: versions before 2.29 or exactly version 2.29 are vulnerable.Affected if The installed version is before 2.29 (Core Update 198) or equals 2.29
-
Verify Dynamic DNS is configuredAccess the IPFire web interface and navigate to Services > Dynamic DNS. Check if any Dynamic DNS hosts are defined. Alternatively, inspect configuration files in /var/ipfire/ddns/ for host configuration entries.Affected if Dynamic DNS hosts exist in the configuration (these are the entries where malicious payloads could be stored)
-
Inspect stored Dynamic DNS valuesReview the SERVICE, LOGIN, and PASSWORD fields for each Dynamic DNS host entry. Look for suspicious patterns such as <script> tags, javascript: URIs, or HTML event handlers (onclick, onerror, etc.) embedded in these fields.Affected if Any Dynamic DNS host contains unsanitized JavaScript or HTML in the SERVICE, LOGIN, or PASSWORD fields
-
Check web interface renderingView the Dynamic DNS page in the web interface as a different user or in a different session. Inspect the page source (right-click > View Page Source) to see if the values are rendered without proper HTML encoding.Affected if The values display with raw HTML/JavaScript characters intact rather than being escaped (e.g., < appears as < instead of <)
A user is affected if they run IPFire versions before 2.29 or exactly 2.29 AND have Dynamic DNS hosts configured with unsanitized values in the SERVICE, LOGIN, or PASSWORD fields that render as executable code.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.29
Upgrade to IPFire 2.29 (Core Update 198) or later. As a compensating control, restrict administrative access to the Dynamic DNS configuration interface and monitor for unauthorized changes.
IPFire 2.29 (Core Update 198)
- 1. Back up the current IPFire configuration via the web interface (System > Backup) or via the command line using the 'setup' or 'backup' utility.
- 2. Download IPFire 2.29 (Core Update 198) or later from the official IPFire download page at https://www.ipfire.org/download.
- 3. Apply the update through the IPFire web interface by navigating to System > Update, or perform a fresh installation if preferred.
- 4. After updating, verify the Dynamic DNS functionality works correctly by creating a new Dynamic DNS host entry.
- 5. Confirm the XSS vulnerability is remediated by attempting to inject JavaScript in the SERVICE, LOGIN, or PASSWORD fields - the input should be properly escaped/rendered as text rather than executed.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-34309 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-34309 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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