Skip to main content
VulnerabilityPublished

CVE-2026-116136: ProjectSend · Incorrect Authorization

Affects ProjectSendSource CVE Database V5

0

Not known to be exploited · CVSS 6.0 Medium.

Data as of 26 Oct 2026, 13:07 UTC

CVSS 4.0 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
projectsendProjectSendAffected
  • >=2.0.0 <=2.7.1
Fixed in–

AI-suggested

Until a fix is available, restrict staff user permissions and monitor file sharing activities closely to mitigate unauthorized access risks.

Description

ProjectSend versions 2.0.0 through 2.7.1 have an incomplete authorization vulnerability in the FileVersions::link() function. This flaw allows staff users to share files without proper authorization by linking file versions improperly. Attackers can exploit this by linking their files to intermediate revisions or assigning clients outside their scope, which causes the moveAssignmentsToRoot() function to expose protected original files to unauthorized clients.

References

Community reviews

Loading reviews…