CVE-2025-11908
BaseFortify
Publication date: 2025-10-17
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 |
|---|---|---|
| streamax | streamax_crocus | 1.3.40 |
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?
This vulnerability is an arbitrary file upload flaw in the Streamax Crocus 1.3.40 system by Shenzhen Ruiming Technology. It exists in the uploadFile function of the /FileDir.do?Action=Upload endpoint, where manipulation of the File argument allows an attacker to upload files without restriction. This means an attacker can remotely upload malicious files, such as scripts, to the server, potentially leading to full server takeover. [1, 2]
How can this vulnerability impact me? :
Exploiting this vulnerability can allow an attacker to upload malicious files remotely without authentication, which may lead to unauthorized access, compromise of confidentiality, integrity, and availability of the system, and potentially full server takeover. This can disrupt operations, lead to data breaches, and cause significant security risks. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring attempts to access the /FileDir.do?Action=Upload endpoint and checking for unusual or unauthorized file upload activity, especially manipulation of the 'File' argument. Network or web server logs can be inspected for POST requests to this endpoint. A simple detection command could be using curl to test the upload functionality, for example: curl -X POST 'http://<target>/FileDir.do?Action=Upload' -F 'File=@testfile' -v to see if the server accepts file uploads without proper restrictions. Additionally, web application firewall (WAF) rules can be configured to alert on such requests. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include disabling or restricting access to the /FileDir.do?Action=Upload endpoint to prevent unauthorized file uploads. Since no vendor patch or countermeasure is available, it is recommended to replace the affected product with an alternative solution. Additionally, monitoring and blocking suspicious upload attempts via network security tools or WAFs can help reduce risk. Applying strict access controls and network segmentation to limit exposure is also advised. [2]