---
id: "CVE-2026-112001"
kind: "vulnerability"
aliases: ["CVE-2026-112001"]
title: "ProjectSend: restricted API token can take over owner account"
severity: "high"
cvss: 8.6
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "php", "projectsend", "self-hosted"]
not_affected_if: ["already-on-2.7.0", "no-api-tokens"]
published_at: "2026-10-18T12:17:12+00:00"
first_seen_at: "2026-10-23T21:57:15+00:00"
updated_at: "2026-10-25T03:00:01+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-112001", "first_seen_at": "2026-10-23T21:57:15+00:00"}]
---

# ProjectSend: restricted API token can take over owner account

ProjectSend versions from 2.0.0 before 2.7.0 let a restricted API token change the token owner's password and clear two-factor authentication via PATCH /api/v1/users/{user}. An attacker can then sign in interactively with the owner's full role permissions.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed ProjectSend version; versions below `2.7.0` are affected.
- Review API tokens that hold `manage_users` and `edit_users` permissions.

## Fix

- Upgrade ProjectSend to `2.7.0` or later.
- Rotate passwords and API tokens for owner accounts if the instance ran an affected version with exposed tokens.

## Timeline

- 2026-10-23T21:57:15+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-112001

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_
