CVE-2026-112002 ProjectSend CVE debrief

Who should care

Defenders responsible for ProjectSend installations should assess exposure and apply patches or compensating controls to prevent unauthorized password changes. This includes verifying the installed version, reviewing relevant monitoring and logs, and implementing compensating controls such as restricting access to the /settings/password endpoint. Security teams should prioritize verifying exposure and applying patches or compensating controls to prevent

Why it matters

CVE-2026-112002 is a high-severity vulnerability in ProjectSend that allows attackers to change local passwords without the current password for social-provisioned accounts, potentially leading to account takeover and unauthorized access.

• Account takeover for social-provisioned accounts
• Unauthorized access to sensitive information
• Potential for lateral movement within the network
• Need for verification of installed versions and exposure

Technical summary

The vulnerability exists in the PasswordController::update() function in ProjectSend versions 2.5.0 before 2.7.0. An attacker with a stolen session cookie can send a PUT request to /settings/password to create a local password and take over the account. The vulnerability allows attackers to change local passwords without the current password for social-provisioned accounts, potentially leading to account takeover and unauthorized access. There is no evidence of public exploitation, but defenders should verify exposure and apply patches or compensating controls.

Defensive priority

Defenders should prioritize verifying exposure and applying patches or compensating controls to prevent unauthorized password changes.

Recommended defensive actions

• Verify exposure by checking if the installed version of ProjectSend is vulnerable
• Apply patches or upgrade to version 2.7.0 or later
• Implement compensating controls such as monitoring for suspicious password change attempts
• Restrict access to the /settings/password endpoint
• Review 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
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is caused by an unverified password change in the PasswordController::update() function. Attackers with a stolen session cookie can send a PUT request to /settings/password to create a local password and take over the account. The vulnerability has been reported in ProjectSend versions 2.5.0 before 2.7.0. There is no evidence of public exploitation, but defenders should verify exposure and apply patches or compensating controls. Limited source information is available, and defenders should review the official CVE

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.