dbcve.org
IpfireApplication

CVE-2025-34301

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 into the COUNTRY_CODE parameter when creating a location group. When a user adds a new location group, the application issues an HTTP POST request with the ACTION parameter set to savelocationgrp, and the value of the COUNTRY_CODE parameter determines the flag displayed for that group. The value of this parameter is stored and later rendered in the web interface without proper sanitization or encoding, allowing malicious scripts to be executed in the context of other users viewing 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 prior to 2.29 contain a stored XSS vulnerability where the COUNTRY_CODE parameter in location group creation (ACTION=savelocationgrp) is not sanitized before storage. When other users view the location group page, the malicious JavaScript embedded in the country code executes in their browser context.

MitigationUpgrade IPFire to version 2.29 (Core Update 198) or later, which includes proper input sanitization for the COUNTRY_CODE 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 IPFire version
    Access the IPFire web interface and navigate to System > Status, or run 'cat /etc/system-release' or 'cat /etc/os-release' on the console to determine the installed IPFire version.
    Affected if The installed version is prior to 2.29 or is exactly version 2.29.
  2. Locate the location group configuration
    Check the IPFire configuration database (typically /var/ipfire/location/location.gz or related files in /var/ipfire/location/) for any stored location group entries.
    Affected if Location group entries exist in the configuration.
  3. Inspect COUNTRY_CODE values
    Examine the stored location group data for the COUNTRY_CODE field. If using the web interface, navigate to the location group page (likely under Services > GeoIP or similar) and view any existing location groups.
    Affected if The COUNTRY_CODE field contains unexpected characters, scripts, or HTML tags that were not entered by an administrator.
  4. Review web server access logs
    Check IPFire web server logs (typically /var/log/httpd/error_log or /var/log/httpd/access_log) for requests containing 'ACTION=savelocationgrp' and examine the COUNTRY_CODE parameter value.
    Affected if Requests with ACTION=savelocationgrp show unsanitized input in the COUNTRY_CODE parameter.

A user is affected if their IPFire version is prior to 2.29 or equals 2.29, and location groups with potentially malicious COUNTRY_CODE values exist in the configuration.

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 includes proper input sanitization for the COUNTRY_CODE parameter.

Recommended fix High confidence

IPFire 2.29 Core Update 198

  1. Identify the current IPFire version and Core Update number by accessing the web interface or running 'lbu status'
  2. Backup the IPFire configuration using 'lbu commit' to preserve settings
  3. Access the IPFire package manager or download the updated IPFire 2.29 Core Update 198 ISO/image from the official IPFire website (www.ipfire.org)
  4. Follow the IPFire upgrade procedure to install Core Update 198, or perform a fresh installation if upgrading across major versions
  5. After upgrading, verify the version by checking the web interface dashboard shows 'IPFire 2.29 - Core Update 198'
  6. Create a test location group to confirm the COUNTRY_CODE parameter is now properly sanitized and no XSS payload executes
Caveat Review IPFire release notes for Core Update 198 to check for any configuration changes or feature modifications that may affect existing setups

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-34301 — 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-34301 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