dbcve.org
IpfireApplication

CVE-2025-34306

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-28
Fix available
A fix is available. Upgrade to 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 pienumber parameter when updating the default firewall IP search values. When a user updates these defaults, the application issues an HTTP POST request to /cgi-bin/logs.cgi/firewalllogip.dat with the default number of IPs in the pienumber 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 page.

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 before 2.29 contain a stored XSS vulnerability where the pienumber parameter in /cgi-bin/logs.cgi/firewalllogip.dat is not sanitized before storage or output encoding when rendered, allowing authenticated attackers to inject arbitrary JavaScript that executes in other users' browser sessions.

MitigationUpgrade to IPFire 2.29 (Core Update 198) or later which implements proper input sanitization and output encoding for the pienumber parameter; as a compensating control, restrict administrative access to the firewall log configuration page.

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 IPFire version
    Access the IPFire web interface and navigate to System > Status, or run 'cat /etc/ipfire/main/version' via SSH to determine the installed version number
    Affected if Version is below 2.29 or exactly 2.29
  2. Confirm firewall logging is enabled
    In the IPFire web UI, go to Logs > Firewall and verify if firewall logging configuration is accessible or active
    Affected if Firewall logging is enabled and the logs page is accessible to authenticated users
  3. Verify user access to logs.cgi
    Check if low-privilege or untrusted users have access to the /cgi-bin/logs.cgi/firewalllogip.dat endpoint via the Logs > Firewall menu
    Affected if Authenticated users other than administrators can access the firewall log interface
  4. Inspect browser session behavior
    If you have access, examine the HTTP response when submitting the pienumber parameter through the firewall log page to see if the value is returned without encoding
    Affected if The pienumber parameter value appears in the response without HTML encoding (showing raw characters like < > & instead of &lt; &gt; &amp;)

You are affected if your IPFire version is 2.29 or earlier and the firewall logging interface is accessible to authenticated users who can inject script content via the pienumber parameter.

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 2.29 or later
Fixed in 2.29
Interim mitigation

Upgrade to IPFire 2.29 (Core Update 198) or later which implements proper input sanitization and output encoding for the pienumber parameter; as a compensating control, restrict administrative access to the firewall log configuration page.

Recommended fix High confidence

IPFire 2.29 (Core Update 198) or later

  1. 1. Back up the IPFire configuration before starting the upgrade process.
  2. 2. Access the IPFire web interface using an administrator account.
  3. 3. Navigate to the System section in the IPFire web UI.
  4. 4. Locate the update or upgrade option and initiate a system update.
  5. 5. Ensure the system upgrades to IPFire version 2.29 (Core Update 198) or a later stable release.
  6. 6. After the upgrade completes, verify the web interface is accessible and functional.
  7. 7. Clear browser cache and test that the firewall log pages render correctly without JavaScript errors.

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

Fix this in Ipfire Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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