# CVE-2025-50975: Cross-site scripting in n/a

> Authenticated administrators can inject persistent JavaScript into IPFire firewall rules, leading to session hijacking and unauthorized actions when viewed by other admins.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A: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:** 26 Aug 2025
- **Updated:** 27 Aug 2025
- **Also known as:** GHSA-c7fh-m339-6279

## What is CVE-2025-50975?

CVE-2025-50975 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Aug 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 2.29 web-based firewall interface (firewall.cgi) fails to sanitize several rule parameters such as PROT, SRC_PORT, TGT_PORT, dnatport, key, ruleremark, src_addr, std_net_tgt, and tgt_addr, allowing an authenticated administrator to inject persistent JavaScript. This stored XSS payload is executed whenever another admin views the firewall rules page, enabling session hijacking, unauthorized actions within the interface, or further internal pivoting. Exploitation requires only high-privilege GUI access, and the complexity of the attack is low.

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

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

It affects 1 product.


Products: Ipfire Ipfire.

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

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

## Is CVE-2025-50975 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50975 exists.

## Other vulnerabilities in n/a

- [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-50975 and fix it if it is affected.

What it is: CVE-2025-50975 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Aug 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50975 exists.

Affected product: n/a. 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-50975/ (Markdown: https://insights.sbomify.com/CVE-2025-50975/index.md)
```

## Sources

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

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