dbcve.org
IpfireApplication

CVE-2025-34302

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 PROT parameter when creating a new service. When a user adds a service, the application issues an HTTP POST request with the ACTION parameter set to saveservice, and the protocol type is specified in the PROT parameter. The value of this parameter is stored and later rendered in the web interface without proper sanitization or encoding, allowing injected scripts to execute in the context of other users viewing the affected service entry.

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 (Core Update 198) have a stored XSS vulnerability in the web interface's service creation function. The PROT parameter in POST requests with ACTION=saveservice is not sanitized before storage, and malicious JavaScript in this field executes when other users view the affected service entry.

MitigationUpgrade to IPFire version 2.29 (Core Update 198) or later, which includes proper input sanitization and output encoding for the PROT 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. Check IPFire version
    Access the IPFire web interface and look at the System page, or run 'cat /etc/system-release' or 'cat /var/ipfire/general-functions.pl' to determine the installed version number and Core Update level
    Affected if The installed version is older than 2.29 (Core Update 198) or exactly version 2.29
  2. Identify saved services with the vulnerable parameter
    Review service configurations in the IPFire web interface under the Services section, or examine stored configuration files for any service entries containing the PROT parameter
    Affected if Service entries exist that were created or modified before upgrading to version 2.29 or later, particularly entries containing HTML or JavaScript characters in the PROT field
  3. Inspect web interface logs for exploit attempts
    Review IPFire web interface logs (typically in /var/log/httpd/error_log or through the Log Viewer in the web UI) for POST requests with ACTION=saveservice containing suspicious values in the PROT parameter
    Affected if Log entries show POST requests to the service creation function with non-alphanumeric or script-like content in the PROT parameter field
  4. Check for unauthorized service entries
    Log into the IPFire web interface and navigate to the Services section to enumerate all defined services, looking for any entries with unexpected or encoded content in protocol/port fields
    Affected if Any service entries exist with visible JavaScript code, HTML tags, or unusual encoded characters in fields that should only contain protocol names like TCP or UDP

A user is affected if their IPFire version is 2.29 or earlier AND the web interface is accessible with privileges to create or view services, since the XSS payload would be stored in the PROT parameter of saved service entries.

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 version 2.29 (Core Update 198) or later, which includes proper input sanitization and output encoding for the PROT parameter.

Recommended fix High confidence

2.29 (Core Update 198)

  1. Log in to the IPFire web interface
  2. Navigate to the System > Update section
  3. Run the update to install Core Update 198 (version 2.29)
  4. Verify the update completed successfully
  5. Reboot the IPFire system if prompted
  6. Confirm the version shows 2.29 (Core Update 198) in the web interface

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

Fix this in Ipfire Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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