Compliance Impact

The provided context and resources do not contain specific information about how this vulnerability affects compliance with common standards and regulations such as GDPR or HIPAA.

Useful 0 Not Useful 0

Executive Summary

CVE-2026-5624 is a security flaw in ProjectSend r2002 affecting the file upload.php component. It is a Cross-Site Request Forgery (CSRF) vulnerability that allows an attacker to trick an authenticated user into unknowingly uploading files by exploiting a bypass in CSRF validation. The vulnerability arises because the upload endpoint accepted parameters from both GET and POST requests and excluded certain requests from CSRF checks, enabling remote attackers to perform unauthorized file uploads.

The issue was fixed by removing the CSRF bypass, enforcing CSRF token validation on every upload chunk, and restricting parameter acceptance strictly to POST requests. This prevents attackers from exploiting the upload functionality without a valid CSRF token.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability can allow attackers to perform unauthorized file uploads on your ProjectSend installation by exploiting an authenticated user's session without their consent. Such unauthorized uploads could lead to the introduction of malicious files, potentially compromising the server or the confidentiality and integrity of your data.

Because the attack can be initiated remotely and without user interaction beyond visiting a malicious page, it increases the risk of exploitation. This could result in unauthorized access, data manipulation, or further attacks leveraging the uploaded files.

Useful 0 Not Useful 0

Detection Guidance

This vulnerability involves a Cross-Site Request Forgery (CSRF) issue on the file upload endpoint of ProjectSend. Detection would involve monitoring for unauthorized or suspicious POST requests to the upload.php endpoint that lack valid CSRF tokens.

You can detect potential exploitation attempts by inspecting HTTP traffic for POST requests to the file upload endpoint that do not include a valid CSRF token or that use GET parameters instead of POST.

Suggested commands to detect such activity might include using network traffic analysis tools or web server logs filtering. For example:

• Using tcpdump or tshark to capture HTTP POST requests to upload.php: tcpdump -A -s 0 'tcp port 80 and (((ip[2:2] - ((ip[0]&0xf)<<2)) - ((tcp[12]&0xf0)>>2)) != 0)' | grep 'POST /upload.php'
• Using grep on web server access logs to find requests to upload.php with GET parameters: grep 'upload.php?' /var/log/apache2/access.log
• Checking for missing CSRF tokens in POST requests might require custom log parsing or application-level logging enhancements.

Useful 0 Not Useful 0

Mitigation Strategies

The primary mitigation step is to upgrade ProjectSend to version r2029 or later, which includes the patch that fixes this CSRF vulnerability.

The patch enforces strict CSRF token validation on all POST requests to the file upload endpoint, removes the previous CSRF bypass, and restricts parameters to be accepted only via POST, thereby preventing unauthorized file uploads.

Additional security improvements in the r2029 release include enhanced cookie security flags and other vulnerability fixes, so upgrading is strongly recommended.

If immediate upgrade is not possible, consider implementing web application firewall (WAF) rules to block suspicious requests to the upload.php endpoint that do not include valid CSRF tokens or that use GET parameters for uploads.

Useful 0 Not Useful 0