CVE-2026-112001 ProjectSend CVE debrief

Who should care

Defenders responsible for ProjectSend installations, especially those using versions 2.0.0 to 2.6.0, should assess exposure and prioritize verification and remediation. They should also review compensating controls for exposed systems while remediation is scheduled and verified.

Why it matters

CVE-2026-112001 is a high-severity vulnerability in ProjectSend that allows restricted API token holders to change token owner's credentials. Defenders should prioritize verifying exposure, especially if using versions 2.0.0 to 2.6.0, and assess potential impact.

• Restricted API token holders can change token owner's credentials
• Potential for attackers to gain interactive access with owner's permissions
• Possible unauthorized access to sensitive information
• Need for verification of affected versions and exposure

Technical summary

CVE-2026-112001 is a high-severity vulnerability in ProjectSend versions 2.0.0 before 2.7.0. It allows restricted API token holders, with manage_users and edit_users permissions, to change the token owner's credentials via PATCH /api/v1/users/{user}. This could enable attackers to set a new owner password, clear two-factor authentication, and gain interactive access with the owner's full role permissions.

Defensive priority

Defenders should prioritize verifying exposure and assessing the impact of this vulnerability on their systems, especially if using ProjectSend versions 2.0.0 to 2.6.0.

Recommended defensive actions

• Verify if using ProjectSend versions 2.0.0 to 2.6.0 and assess exposure
• Restrict API token permissions to prevent unauthorized credential changes
• Monitor for suspicious PATCH /api/v1/users/{user} requests
• Update to ProjectSend version 2.7.0 or later if possible
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The vulnerability is confirmed in ProjectSend versions 2.0.0 to 2.6.0. Official sources include CVE Program, NVD, and Vulncheck. The CVE record was published on 2026-10-18T12:17:12.140Z and has not been modified since then. The vulnerability allows restricted API token holders to change the token owner's credentials via PATCH /api/v1/users/{user}. This could enable attackers to set a new owner password, clear two-factor authentication, and gain interactive access with the owner's full role permissions. The vulnerability has a CVSS

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.