# CVE-2026-116136: ProjectSend incomplete authorization in FileVersions::link()

Source: https://junglewise.ai/threats/cve-2026-116136-projectsend-2-0-0-through-2-7-1-contains-an-incomplete  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-25. Updated: 2026-10-25  
License: CC BY 4.0 with a link back

CVE-2026-116136 · Severity: medium · CVSS 5.9 · Published 2026-10-25

ProjectSend is an open-source file-sharing platform that allows organizations to securely share documents with clients. A vulnerability in the file versioning feature allows staff users to bypass authorization controls and share files with unauthorized clients by manipulating file version links, potentially exposing sensitive documents to unintended recipients.

Technologies: [ProjectSend](https://junglewise.ai/threats/technologies/projectsend). Vendors: [ProjectSend](https://junglewise.ai/threats/vendors/projectsend).

## Quick answers

**Is CVE-2026-116136 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-116136 being exploited in the wild.

**How severe is CVE-2026-116136?** Medium severity, with a CVSS score of 5.9, published 25 October 2026.

**Which products and versions are affected?** ProjectSend 2.0.0 through 2.7.1.

**Is there a fix for CVE-2026-116136?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-116136 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-116136?** Check whether you run ProjectSend at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The FileVersions::link() method in ProjectSend contains incomplete authorization checks that fail to properly validate staff user permissions when linking file versions. An attacker with staff privileges can exploit this by linking to intermediate file revisions or assigning out-of-scope clients, which causes the moveAssignmentsToRoot() function to expose protected original files to unauthorized clients. The vulnerability requires authentication as a staff user.

## Affected products

- ProjectSend ProjectSend 2.0.0 through 2.7.1

## Timeline

- 2026-10-25: disclosed

## References

- [https://github.com/projectsend/projectsend](https://github.com/projectsend/projectsend)
- [https://github.com/projectsend/projectsend/blob/v2.7.1/app/Modules/Files/Versions/FileVersions.php](https://github.com/projectsend/projectsend/blob/v2.7.1/app/Modules/Files/Versions/FileVersions.php)

## Related threats

- [ProjectSend path validation flaw in OrphanFileScanner](https://junglewise.ai/threats/cve-2026-112003-projectsend-2-0-0-before-2-7-0-contains-a-path-validation-flaw)
- [ProjectSend password change authentication bypass in social-provisioned accounts](https://junglewise.ai/threats/cve-2026-112002-projectsend-2-5-0-before-2-7-0-contains-an-unverified-password)
- [ProjectSend authorization bypass via API token privilege escalation](https://junglewise.ai/threats/cve-2026-112001-projectsend-2-0-0-before-2-7-0-contains-an-incorrect)
- [ProjectSend stored XSS in files-edit.php](https://junglewise.ai/threats/cve-2021-47947-projectsend-stored-xss-in-files-edit-php)
- [ProjectSend CSRF in file upload endpoint](https://junglewise.ai/threats/cve-2026-5624-projectsend-csrf-in-file-upload-endpoint)