---
id: "CVE-2026-116136"
kind: "vulnerability"
aliases: ["CVE-2026-116136"]
title: "ProjectSend: staff can share protected files through version linking"
severity: "medium"
cvss: 6.0
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "php", "projectsend", "self-hosted"]
not_affected_if: ["unknown"]
published_at: "2026-10-25T12:16:30+00:00"
first_seen_at: "2026-10-25T12:40:44+00:00"
updated_at: "2026-10-25T12:41:31+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-116136", "first_seen_at": "2026-10-25T12:40:44+00:00"}]
---

# ProjectSend: staff can share protected files through version linking

ProjectSend 2.0.0 through 2.7.1 has an incomplete authorization check in FileVersions::link(), so a staff user can link file versions to share files they should not. An attacker with a staff account can expose protected original files to clients outside their scope.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed ProjectSend version in the application's config or footer, and see whether it falls between `2.0.0` and `2.7.1`
- unknown for other checks, the sources do not say

## Fix

- Upgrade ProjectSend to a release later than `2.7.1`; the sources do not name the fixed version
- unknown for other actions, the sources do not say

## Timeline

- 2026-10-25T12:40:44+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-116136

## From the sources

ProjectSend 2.0.0 through 2.7.1 contains an incomplete authorization vulnerability in FileVersions::link() that allows staff users to share files without authorization by linking file versions. Attackers can link their file onto an intermediate revision or assign out-of-scope clients, causing moveAssignmentsToRoot() to expose protected original files to unauthorized clients.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_