dbcve.org
IpfireApplication

CVE-2025-34313

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 QUOTA_USERS parameter when creating a user quota rule. When a user adds a new user quota rule the application issues an HTTP POST request to /cgi-bin/urlfilter.cgi with the MODE parameter set to USERQUOTA and the assigned user(s) provided in the QUOTA_USERS 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 quota 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 prior to 2.29 (Core Update 198) contain a stored XSS vulnerability in the user quota rule functionality. The QUOTA_USERS parameter in POST requests to /cgi-bin/urlfilter.cgi (MODE=USERQUOTA) is not sanitized before storage, and rendered without proper encoding in the web interface, allowing injected JavaScript to execute in other users' browser sessions.

MitigationUpgrade to IPFire 2.29 (Core Update 198) or later which implements proper input sanitization and output encoding for the QUOTA_USERS 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 UI and look at the System page for the Core Update version number, or run 'cat /etc/ipfire/main/version' on the console
    Affected if Version is shown as less than 2.29 or exactly 2.29 (Core Update 198)
  2. Verify URL filter module is installed
    Check if the URL filter package is installed via the IPFire web UI under 'Pakete' (Packages) or by checking for /usr/lib/urlfilter/ directory on the filesystem
    Affected if URL filter add-on is installed and enabled
  3. Confirm user quota feature is configured
    Log into the web UI and navigate to the URL Filter settings. Look for 'User Quota' or 'Quota Users' section under the quota rules configuration
    Affected if User quota rules have been created and are active in the URL filter module
  4. Inspect stored quota user entries for malicious scripts
    Access the URL filter configuration file (typically /var/ipfire/urlfilter/settings or database) and examine any stored QUOTA_USERS values for script tags, JavaScript event handlers, or encoded payloads
    Affected if Any QUOTA_USERS entry contains HTML tags like <script>, javascript:, onerror=, or other XSS payload patterns

A user is affected if their IPFire version is 2.29 or earlier AND the URL filter with user quota functionality is enabled and contains unsanitized script content in quota user 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 2.29 (Core Update 198) or later which implements proper input sanitization and output encoding for the QUOTA_USERS parameter.

Recommended fix High confidence

IPFire 2.29 Core Update 199 or later

  1. 1. Access the IPFire administrative web interface.
  2. 2. Navigate to the System section and select Update from the menu.
  3. 3. Click the 'Update' button to check for and install the latest core updates.
  4. 4. Alternatively, if using command-line access, run 'pakfire update' followed by 'pakfire upgrade' to fetch and apply updates.
  5. 5. Verify that the system is updated to Core Update 199 or later, which contains the fix for CVE-2025-34313.
  6. 6. After updating, clear browser cache and test that the QUOTA_USERS parameter properly sanitizes input in the URL Filter user quota configuration page.
Caveat Standard IPFire core update - review release notes for any configuration changes

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
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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