CVE-2026-116136Medium· 5.9▾ SunlitProjectSend 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 inter…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 32.5 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
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.
ProjectSend >= 2.0.0 <= 2.7.1Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-112001High· 7.2ProjectSend 2.0.0 before 2.7.0 Incorrect Authorization via Users API Token Abilities
CVE-2026-112002Medium· 6.8ProjectSend 2.5.0 before 2.7.0 Unverified Password Change via /settings/password
CVE-2026-112003Medium· 5.9ProjectSend 2.0.0 before 2.7.0 Path Validation Bypass via Orphan File Import/Delete
CVE-2024-11680Critical· 9.8ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability
CVE-2020-28874High· 7.5reset-password.php in ProjectSend before r1295 allows remote attackers to reset a password because of incorrect business logic
CVE-2025-67740Low· 2.7In JetBrains TeamCity before 2025.11 improper access control could expose GitHub App token's metadata