dbcve.org
IpfireApplication

CVE-2025-34314

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 SRC, DST, and COMMENT parameters when creating a time constraint rule. When a user adds a time constraint rule the application issues an HTTP POST request to /cgi-bin/urlfilter.cgi with the MODE parameter set to TIMECONSTRAINT and the source hostnames/IPs, destination, and remark provided in the SRC, DST, and COMMENT parameters respectively. The values of these parameters are 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 time constraint 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 urlfilter.cgi web interface. Authenticated attackers can inject malicious JavaScript via the SRC, DST, and COMMENT parameters when creating time constraint rules (MODE=TIMECONSTRAINT). These values are stored without sanitization and rendered in the web interface without proper encoding, allowing the injected script to execute in the browsers of other users who view the affected time constraint entries.

MitigationUpgrade IPFire to version 2.29 (Core Update 198) or later. If immediate upgrade is not possible, implement input validation and output encoding for the SRC, DST, and COMMENT parameters in the urlfilter.cgi timECONSTRAINT handling code.

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
    Examine /etc/system-release or /srv/web/ipfire/cgi-bin/../conf/mainversion to identify the installed IPFire version
    Affected if The version is lower than 2.29 or equals 2.29 (Core Update 198)
  2. Verify URLFilter module is present
    Confirm the urlfilter.cgi script exists in /srv/web/ipfire/cgi-bin/ and check for the urlfilter database in /var/ipfire/urlfilter/
    Affected if The URLFilter module is installed and accessible to authenticated users
  3. Identify time constraint rules in URLFilter
    Examine the URLFilter database (typically SQLite at /var/ipfire/urlfilter/urlfilter.db) for entries where MODE=TIMECONSTRAINT, checking the SRC, DST, and COMMENT fields for stored values
    Affected if Any time constraint rules exist in the URLFilter configuration
  4. Inspect stored parameter values for unsanitized content
    Query the urlfilter database tables (such as time table) for the SRC, DST, and COMMENT columns and review their contents for HTML/script tags or unusual encoded characters
    Affected if The stored values in SRC, DST, or COMMENT fields contain raw HTML, JavaScript tags, or unescaped special characters that could execute in a browser

A user is affected if their IPFire version is 2.29 or lower AND the URLFilter module contains time constraint rules with unsanitized values in the SRC, DST, or COMMENT parameters.

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. If immediate upgrade is not possible, implement input validation and output encoding for the SRC, DST, and COMMENT parameters in the urlfilter.cgi timECONSTRAINT handling code.

Recommended fix High confidence

IPFire 2.29 (Core Update 198)

  1. Upgrade IPFire to version 2.29 (Core Update 198) which contains the fix for this stored XSS vulnerability
  2. Apply the upgrade through the IPFire web interface or standard update mechanism
  3. Verify the upgrade was successful by checking the IPFire version

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