# CVE-2025-2305: Local file inclusion vulnerability in LIVE CONTRACT

> Unauthenticated attackers can exploit a path traversal flaw to download arbitrary files from the server.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 May 2025
- **Updated:** 16 May 2025
- **Also known as:** GHSA-f58m-h66f-qwjr

## What is CVE-2025-2305?

CVE-2025-2305 is a high-severity path traversal vulnerability in SYNCPILOT LIVE CONTRACT, published on 16 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Path traversal vulnerability in the file
download functionality was identified. This vulnerability allows
unauthenticated users to download arbitrary files, in the context of the
application server, from the Linux server.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2025-2305 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2305 is a high-severity path traversal vulnerability in SYNCPILOT LIVE CONTRACT, published on 16 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2305 in the wild and no public exploit code.

Affected product: SYNCPILOT LIVE CONTRACT. 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-2305/ (Markdown: https://insights.sbomify.com/CVE-2025-2305/index.md)
```

## Sources

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

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