dbcve.org
IpfireApplication

CVE-2025-34303

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 IGNORE_ENTRY_REMARK parameter when adding a whitelisted host. When a whitelisted host is added, an HTTP POST request is sent to the Request-URI /cgi-bin/ids.cgi and the remark for the entry is provided in the IGNORE_ENTRY_REMARK 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 who view the affected whitelist 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

A stored cross-site scripting (XSS) vulnerability in IPFire versions prior to 2.29 allows authenticated attackers to inject arbitrary JavaScript via the IGNORE_ENTRY_REMARK parameter when adding whitelisted hosts. The parameter value is stored without sanitization and rendered unsafely in the web interface at /cgi-bin/ids.cgi, executing in the context of other users who view the whitelist entry.

MitigationUpgrade to IPFire 2.29 (Core Update 198) or later, which includes proper input sanitization and output encoding for the IGNORE_ENTRY_REMARK 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 navigate to System > Status, or run 'cat /etc/version' via SSH to determine the installed IPFire version.
    Affected if The installed version is 2.29 (Core Update 198) or any version prior to 2.29.
  2. Verify IDS module is enabled
    Log into the IPFire web interface and check if the Intrusion Detection System (IDS) module is installed and enabled under Services > IDS.
    Affected if The IDS module is enabled and the whitelist functionality is accessible.
  3. Inspect whitelist entries in IDS
    Navigate to /cgi-bin/ids.cgi in the web interface and examine any whitelist entries (whitelisted hosts). Look for the 'Remark' or comment field associated with each entry.
    Affected if There are existing whitelist entries with unsanitized remarks that may contain script tags or malicious JavaScript.
  4. Review stored IGNORE_ENTRY_REMARK values
    If you have CLI access, examine the IDS configuration files in /var/ipfire/ or related directories for whitelist entries containing the IGNORE_ENTRY_REMARK parameter values.
    Affected if Any whitelist entry contains raw, unsanitized input in the remark field that includes HTML or JavaScript syntax.

You are affected if your IPFire version is 2.29 or earlier, the IDS module is enabled, and there are whitelist entries with unsanitized remarks that could execute JavaScript when viewed by other users.

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 includes proper input sanitization and output encoding for the IGNORE_ENTRY_REMARK parameter.

Recommended fix High confidence

IPFire 2.29 (Core Update 198) or later

  1. 1. Log into the IPFire administrative web interface
  2. 2. Navigate to the System menu and select 'Backup' to create a configuration backup
  3. 3. Navigate to 'System' > 'Update' to check for available updates
  4. 4. If not already at version 2.29 (Core Update 198) or later, apply the update to upgrade to the fixed release
  5. 5. After upgrading, verify the IDS/Whitelist functionality works correctly
  6. 6. Confirm the IGNORE_ENTRY_REMARK parameter is now properly sanitized when adding whitelisted hosts
Caveat Standard IPFire update; ensure configuration backup before upgrading

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

Fix this in Ipfire Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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