# CVE-2026-112001: ProjectSend 2.0.0 before 2.7.0 Incorrect Authorization via Users API Token Abilities

> Attackers with restricted API tokens can modify owner credentials and bypass two-factor authentication to gain full administrative access.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-7c3c-3r99-phc3, GHSA-j5cp-r8pr-m5cr

## What is CVE-2026-112001?

CVE-2026-112001 is a high-severity missing authorization vulnerability in ProjectSend, published on 18 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-112001?


## How do I fix CVE-2026-112001?

No fix has been published for CVE-2026-112001 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-112001 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112001 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-112001 and fix it if it is affected.

What it is: CVE-2026-112001 is a high-severity missing authorization vulnerability in ProjectSend, published on 18 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112001 exists.

Affected product: ProjectSend. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-112001/ (Markdown: https://insights.sbomify.com/CVE-2026-112001/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-112001
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-112001
- OSV: https://osv.dev/vulnerability/CVE-2026-112001

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-112001/
Summaries are generated and may contain mistakes; the official description above is the record.