# CVE-2026-112003: ProjectSend 2.0.0 before 2.7.0 Path Validation Bypass via Orphan File Import/Delete

> Staff users can bypass path validation to delete or adopt other users' files via orphan file endpoints, compromising data integrity and access controls.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:L/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:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-f5fh-phpc-hrv4, GHSA-pv88-7863-5hwq

## What is CVE-2026-112003?

CVE-2026-112003 is a medium-severity path traversal vulnerability in ProjectSend, published on 18 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ProjectSend 2.0.0 before 2.7.0 contains a path validation flaw in OrphanFileScanner::isOrphan() that allows staff with import_orphans permission to treat tracked files as orphans. Attackers can submit ./ path aliases to the orphans import or delete endpoints, deleting or adopting other owners' files while bypassing delete_others_files.

Weakness: CWE-180 (Incorrect Behavior Order: Validate Before Canonicalize)

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


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

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

## Is CVE-2026-112003 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112003 is a medium-severity path traversal vulnerability in ProjectSend, published on 18 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112003 exists.

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

## Sources

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

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