CVE-2023-53905
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-1236 | The product saves user-provided information into a Comma-Separated Value (CSV) file, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as a command when the file is opened by a spreadsheet product. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a CSV injection in ProjectSend r1605 that allows authenticated users to insert malicious formulas into user profile names. When administrators export action logs as CSV files, these formulas can execute code, potentially leading to unauthorized actions.
How can this vulnerability impact me? :
The vulnerability can lead to code execution when CSV files containing malicious formulas are opened by administrators. This can result in unauthorized actions, data compromise, or further exploitation within the system.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for malicious formula payloads in user profile name fields, such as entries starting with '=' followed by suspicious commands like '=calc|a!z|'. One way to detect it is to review user account data or exported CSV files for such injected formulas. Since the vulnerability involves CSV exports, you can inspect exported CSV files for cells starting with '=' that contain unexpected or suspicious content. Specific commands are not provided, but manual inspection or scripts that scan CSV files for formula patterns (e.g., grep '^=' *.csv) can help identify potential injections. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include sanitizing or neutralizing user input fields that are exported to CSV files to prevent formula injection. This can involve escaping or prefixing potentially dangerous characters (like '=' at the start of fields) in user profile names before exporting. Additionally, restrict the ability to export CSV files to trusted administrators and educate users to avoid opening CSV files from untrusted sources. Updating to a version of ProjectSend that addresses this vulnerability, if available, is also recommended. [1, 3]