CVE-2026-112001: ProjectSend 2.0.0 before 2.7.0 Incorrect Authorization via Users API Token Abilities
Fixed in 2.7.0 · Affected: ProjectSend before 2.7.0 · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 50% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- ProjectSend · ProjectSendfrom 2.0.0 before 2.7.0
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- ProjectSend
- Published
- October 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-112001 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.