CVE-2025-11912
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-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a SQL injection flaw found in Shenzhen Ruiming Technology Streamax Crocus version 1.3.40. It exists in the Query function of the endpoint /DeviceState.do?Action=Query, where manipulation of the orderField parameter allows an attacker to inject malicious SQL commands. This can be exploited remotely and the exploit has been publicly disclosed. [2]
How can this vulnerability impact me? :
The vulnerability allows remote attackers to perform SQL injection, which can lead to unauthorized access, data leakage, data modification, or disruption of the affected system. This can compromise the confidentiality, integrity, and availability of the system and its data. [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring and analyzing requests to the endpoint `/DeviceState.do?Action=Query` for suspicious manipulation of the `orderField` parameter that may indicate SQL injection attempts. Network intrusion detection systems (NIDS) or web application firewalls (WAF) can be configured to alert on such patterns. Specific commands to detect this might include using tools like curl or wget to test the endpoint with SQL injection payloads, or using log analysis commands such as `grep` to search for suspicious `orderField` values in web server logs. For example, a command to search logs could be: `grep 'orderField=' /var/log/httpd/access_log` or `grep 'orderField=' /var/log/nginx/access.log` to identify potentially malicious requests. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the vulnerable endpoint `/DeviceState.do?Action=Query` by implementing network-level controls such as IP whitelisting or firewall rules, and deploying a web application firewall (WAF) to detect and block SQL injection attempts targeting the `orderField` parameter. Additionally, monitoring logs for suspicious activity and disabling or restricting the affected functionality if possible can reduce risk. Since the vendor has not responded, applying input validation and sanitization on the server side or using parameterized queries in the application code would be necessary long-term fixes. Until patches are available, these defensive measures are critical. [2]