Auth bypass in Projectsend
CVE-2026-112001
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.
Vulnerability class: Broken Access Control
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.2 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
Weakness classification (CWE)
References
- github.com/projectsend/projectsend/security/advisories/GHSA-j5cp-r8pr-m5cr (vendor-advisory)
- github.com/projectsend/projectsend/commit/db65731c3ad28ac7f0d541c60cb65eb100958… (patch)
- github.com/projectsend/projectsend/releases/tag/v2.7.0 (release-notes)
- github.com/projectsend/projectsend/blob/v2.6.0/app/Modules/Identity/StaffAccoun… (technical-description)
- www.vulncheck.com/advisories/projectsend-2.0.0-before-2.7.0-incorrect-authoriza… (third-party-advisory)
Frequently asked questions
- What is CVE-2026-112001?
- CVE-2026-112001 is a high-severity vulnerability in Projectsend, classified under Incorrect Authorization. CVSS score: 7.2/10. Published 2026-10-18.
- How severe is CVE-2026-112001?
- High severity. CVSS v3 base score is 7.2 out of 10.