dbcve.org
IpfireApplication

CVE-2025-34307

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 firewall country search defaults. When a user updates the default values for the firewall country search, the application issues an HTTP POST request to /cgi-bin/logs.cgi/firewalllogcountry.dat and the default number of countries to display is provided 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 firewall country search settings.

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 contain a stored XSS vulnerability in the firewall country search settings. An authenticated attacker can inject arbitrary JavaScript via the pienumber parameter in a POST request to /cgi-bin/logs.cgi/firewalllogcountry.dat. The injected payload is stored and rendered without sanitization, executing in the context of other users who view the affected settings.

MitigationUpgrade IPFire to version 2.29 (Core Update 198) or later, which contains the patch for this vulnerability. Until upgraded, restrict access to the firewall country search settings to trusted administrators only.

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. Check IPFire version
    Access the IPFire web interface and navigate to the System page, or run 'rpm -q ipfire' or 'cat /etc/system.cfg' from the console to determine the installed version.
    Affected if The installed version is any version prior to 2.29, or exactly version 2.29 (Core Update 198). Versions 2.29 (Core Update 199) and later are not affected.
  2. Verify firewall country search feature
    In the IPFire web interface, navigate to the Logs section and check if the firewall country search settings (firewalllogcountry.dat) are accessible or have been configured.
    Affected if The feature is present and accessible to authenticated users.
  3. Inspect configuration for suspicious entries
    Examine the configuration files or database where the firewall country search settings are stored. Look for any unexpected or encoded content in fields related to the pienumber parameter.
    Affected if Any unsanitized JavaScript or HTML tags are found stored in the configuration, particularly in fields associated with the country search pienumber parameter.

A user is affected if their IPFire installation is version 2.29 or earlier AND the firewall country search feature is accessible to authenticated users who could inject malicious payloads 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 IPFire to version 2.29 (Core Update 198) or later, which contains the patch for this vulnerability. Until upgraded, restrict access to the firewall country search settings to trusted administrators only.

Recommended fix High confidence

IPFire 2.29 Core Update 199 or later

  1. 1. Access the IPFire administrative interface
  2. 2. Navigate to the System section and select 'Force update' or check for available updates
  3. 3. Ensure the system updates to Core Update 199 or later (IPFire version > 2.29)
  4. 4. After updating, verify the version by checking the IPFire web interface dashboard
  5. 5. Confirm the fix by testing the pienumber parameter in /cgi-bin/logs.cgi/firewalllogcountry.dat to ensure proper input sanitization is now in place
Caveat Standard IPFire upgrade precautions apply - ensure backups of configuration are made before updating

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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