CVE-2025-8128
BaseFortify
Publication date: 2025-07-25
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| zhousg | letao | * |
| node.js | formidable | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-434 | The product allows the upload or transfer of dangerous file types that are automatically processed within its environment. |
| CWE-284 | The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-8128 is a critical arbitrary file upload vulnerability in the 'letao' project. It arises from insecure file upload validation in the file routes\bf\product.js, specifically involving the argument 'pictrdtz'. The application uses the 'formidable' library with the 'keepExtensions' option set to true, but fails to properly validate uploaded file types. This allows attackers to upload malicious files with arbitrary extensions, including server-side scripts (e.g., PHP, JSP) or client-side files (e.g., HTML, PDF) containing malicious scripts. As a result, attackers can execute stored Cross-Site Scripting (XSS) attacks or potentially achieve remote code execution (RCE) on the server. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have serious impacts including allowing attackers to upload and execute malicious files on the server, leading to remote code execution (RCE). It also enables stored Cross-Site Scripting (XSS) attacks against users by uploading malicious client-side files. These attacks can compromise the confidentiality, integrity, and availability of the affected system, potentially resulting in unauthorized access, data breaches, or system takeover. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection can focus on monitoring for unusual or unauthorized file uploads to the server, especially to the directory "public/upload/product". Since the vulnerability involves the upload parameter names pic1, pic2, pic3, and arbitrary parameter names still result in file saving, inspecting HTTP POST requests to the endpoint "/addProductPic" for these parameters or unexpected file uploads is recommended. Commands to detect suspicious files could include scanning the upload directory for recently added files with unusual or executable extensions (e.g., .php, .jsp, .html) using commands like: `ls -l --time-style=full-iso public/upload/product | grep -E '\.(php|jsp|html|pdf)$'` or `find public/upload/product -type f -mtime -1` to find files uploaded in the last day. Additionally, reviewing web server logs for POST requests to "/addProductPic" with file upload activity can help. Network monitoring tools or web application firewalls could be configured to alert on such uploads. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include disabling or restricting file uploads to the vulnerable endpoint "/addProductPic" until a fix is applied. Implement strict server-side validation of uploaded files, including checking file types and extensions, and disallowing executable or script files. Consider setting the formidable library's keepExtensions option to false or enhancing validation logic to prevent arbitrary file extensions. If possible, restrict upload permissions and isolate the upload directory from execution privileges to prevent uploaded files from being executed. Monitoring and removing any suspicious files already uploaded is also advised. Since no official patches or mitigations are currently available, consider replacing the affected product with a secure alternative or applying custom patches to fix the validation logic. [2, 3]