CVE-2023-53930
BaseFortify
Publication date: 2025-12-17
Last updated on: 2025-12-27
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| projectsend | projectsend | r1605 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-639 | The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an insecure direct object reference in ProjectSend r1605 that allows unauthenticated attackers to download private files by manipulating the 'id' parameter in the download request to process.php. By changing this parameter, attackers can access any user's private files without authorization.
How can this vulnerability impact me? :
The vulnerability can lead to unauthorized access and disclosure of private files, compromising confidentiality and potentially exposing sensitive information to attackers without authentication.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by attempting to access private files through manipulation of the 'id' parameter in the download request to process.php. A simple test command would be to send a GET request to the endpoint `/process.php?do=download&id=[file_id]` with different file IDs to check if unauthorized files can be downloaded. For example, using curl: `curl -v "http://targetsite/process.php?do=download&id=1"` and changing the id value to see if files belonging to other users are accessible without authentication. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the download functionality by implementing proper authorization checks on the 'id' parameter to ensure users can only download their own files. Until a patch is applied, consider disabling the download feature or restricting access to authenticated and authorized users only. Monitoring and logging download requests for suspicious activity is also recommended. [2]