# CVE-2025-7107: SimStudioAI sim route.ts handleLocalFile path traversal

> Attackers can exploit a path traversal vulnerability in SimStudioAI sim to read arbitrary files from the server.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jul 2025
- **Updated:** 7 Jul 2025
- **Also known as:** GHSA-cwqg-729v-5fg2

## What is CVE-2025-7107?

CVE-2025-7107 is a medium-severity path traversal vulnerability in SimStudioAI sim, published on 7 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability classified as critical has been found in SimStudioAI sim up to 0.1.17. Affected is the function handleLocalFile of the file apps/sim/app/api/files/parse/route.ts. The manipulation of the argument filePath leads to path traversal. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The patch is identified as b2450530d1ddd0397a11001a72aa0fde401db16a. It is recommended to apply a patch to fix this issue.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Sim Sim.

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

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

## Is CVE-2025-7107 being exploited?

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

## Other vulnerabilities in SimStudioAI sim

- [CVE-2026-3431](https://insights.sbomify.com/CVE-2026-3431/): Sim Studio AI - MongoDB SSRF and Arbitrary Document Deletion (critical 9.8)
- [CVE-2026-3432](https://insights.sbomify.com/CVE-2026-3432/): Sim Studio AI - Unauthenticated OAuth Token Theft (critical 9.3)
- [CVE-2025-15099](https://insights.sbomify.com/CVE-2025-15099/): simstudioai sim CRON Secret internal.ts improper authentication (medium 6.9)
- [CVE-2025-7114](https://insights.sbomify.com/CVE-2025-7114/): SimStudioAI sim Session route.ts POST missing authentication (medium 6.9)
- [CVE-2025-10096](https://insights.sbomify.com/CVE-2025-10096/): SimStudioAI sim route.ts server-side request forgery (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7107 is a medium-severity path traversal vulnerability in SimStudioAI sim, published on 7 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-7107 exists.

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

## Sources

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

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