# CVE-2025-34313: IPFire < v2.29 Stored XSS via User Quota Rule URL Filter

> An authenticated attacker can inject arbitrary JavaScript into user quota rules, leading to script execution in other users' browsers.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Oct 2025
- **Updated:** 28 Oct 2025
- **Also known as:** GHSA-rqxx-q98j-rh75

## What is CVE-2025-34313?

CVE-2025-34313 is a medium-severity cross-site scripting vulnerability in IPFire.org IPFire, published on 28 Oct 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-34313?

It affects 1 product.


Products: Ipfire Ipfire.

## How do I fix CVE-2025-34313?

No fix has been published for CVE-2025-34313 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-34313 being exploited?

There is no known exploitation of CVE-2025-34313 in the wild and no public exploit code.

## Other vulnerabilities in IPFire.org IPFire

- [CVE-2021-33393](https://insights.sbomify.com/CVE-2021-33393/): Privilege escalation in n/a (high 8.8)
- [CVE-2018-16232](https://insights.sbomify.com/CVE-2018-16232/): Command injection in n/a (high 8.8)
- [CVE-2017-9757](https://insights.sbomify.com/CVE-2017-9757/): Command injection in n/a (high 8.8)
- [CVE-2025-34311](https://insights.sbomify.com/CVE-2025-34311/): IPFire < v2.29 Command Injection via Proxy Report Creation (high 8.7)
- [CVE-2025-34312](https://insights.sbomify.com/CVE-2025-34312/): IPFire < v2.29 Command Injection via URL Filter Blacklist (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-34313 and fix it if it is affected.

What it is: CVE-2025-34313 is a medium-severity cross-site scripting vulnerability in IPFire.org IPFire, published on 28 Oct 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-34313 in the wild and no public exploit code.

Affected product: IPFire.org IPFire. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-34313/ (Markdown: https://insights.sbomify.com/CVE-2025-34313/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-34313
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-34313
- OSV: https://osv.dev/vulnerability/CVE-2025-34313

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-34313/
Summaries are generated and may contain mistakes; the official description above is the record.