Quick answers
- Is CVE-2026-112001 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-112001 being exploited in the wild.
- How severe is CVE-2026-112001?
- High severity, with a CVSS score of 7.2, published 18 October 2026.
- Which products and versions are affected?
- ProjectSend 2.0.0 before 2.7.0.
- Is there a fix for CVE-2026-112001?
- Yes: fixed in ProjectSend 2.7.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-112001 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-112001?
- Check whether you run ProjectSend at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: ProjectSend 2.7.0
Technical details
The vulnerability is an incorrect authorization flaw in the PATCH /api/v1/users/{user} endpoint that fails to prevent restricted API tokens (limited to manage_users and edit_users permissions) from modifying the owner's own password, email, and two-factor authentication settings. An authenticated attacker with a restricted token can escalate to full owner privileges and access all account data. The fix restricts credential changes via API to prevent token holders from modifying their own sensitive attributes.
Affected products
- ProjectSend ProjectSend 2.0.0 before 2.7.0
Timeline
- 2026-10-18: disclosed
- 2026-10-03: patched