# CVE-2025-2069: Cross-site scripting in Client

> A cross-site scripting vulnerability in the FileZ client allows code execution when a local user visits a crafted URL.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Apr 2025
- **Updated:** 25 Apr 2025
- **Also known as:** GHSA-2ww5-c4rg-76jh

## What is CVE-2025-2069?

CVE-2025-2069 is a medium-severity cross-site scripting vulnerability in FileZ Client, published on 25 Apr 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A cross-site scripting vulnerability was reported in the FileZ client that could allow execution of code if a crafted url is visited by a local user.

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

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


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

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

## Is CVE-2025-2069 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2069 is a medium-severity cross-site scripting vulnerability in FileZ Client, published on 25 Apr 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-2069 in the wild and no public exploit code.

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

## Sources

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

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