# CVE-2026-13381: VSee Clinic and API Insecure Direct Object Reference in File API Allows Unauthorized File Access and Deletion

> An authenticated attacker can manipulate request parameters to access and delete other users' files via the VSee Clinic API.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jul 2026
- **Updated:** 21 Jul 2026
- **Also known as:** GHSA-5xwg-q2hm-f263

## What is CVE-2026-13381?

CVE-2026-13381 is a high-severity missing authorization vulnerability in VSee Clinic, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

VSee Clinic 7.1.26 and API 1.3.0 contain an Insecure Direct Object Reference (IDOR) vulnerability in the /v1.3.0/api/files endpoint. An authenticated attacker can manipulate the 'remark' request parameter to enumerate, retrieve, and delete files belonging to other users on the application server.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-13381?

It affects 2 products.


Products: Vsee Clinic, Vsee Clinic Api.

## How do I fix CVE-2026-13381?

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

## Is CVE-2026-13381 being exploited?

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

## Other vulnerabilities in VSee Clinic

- [CVE-2026-13380](https://insights.sbomify.com/CVE-2026-13380/): VSee Clinic and API Exposes Cleartext SFTP Credentials in Unauthenticated HTTP Responses (critical 9.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-13381 and fix it if it is affected.

What it is: CVE-2026-13381 is a high-severity missing authorization vulnerability in VSee Clinic, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-13381 in the wild and no public exploit code.

Affected product: VSee Clinic. 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-2026-13381/ (Markdown: https://insights.sbomify.com/CVE-2026-13381/index.md)
```

## Sources

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

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