CVE-2026-112001
ProjectSend 2.0.0 before 2.7.0 contains an incorrect authorization …
ProjectSend 2.0.0 before 2.7.0 contains an incorrect authorization vulnerability that allows restricted API token holders to change the token owner's credentials via PATCH /api/v1/users/{user}. Attackers with a token limited to manage_users and edit_users can set a new owner password, clear two-factor authentication, and sign in interactively with the owner's full role permissions.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/projectsend/projectsend/blob/v2.6.0/app/Modules/Identity/StaffAccounts.php#L153
- github.com/projectsend/projectsend/commit/db65731c3ad28ac7f0d541c60cb65eb100958514
- github.com/projectsend/projectsend/releases/tag/v2.7.0
- github.com/projectsend/projectsend/security/advisories/GHSA-j5cp-r8pr-m5cr
- www.vulncheck.com/advisories/projectsend-2.0.0-before-2.7.0-incorrect-authorization-via-us
- nvd.nist.gov/vuln/detail/CVE-2026-112001
- cve.org/CVERecord?id=CVE-2026-112001
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.