CVE-2025-11909
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?
CVE-2025-11909 is a SQL injection vulnerability in Shenzhen Ruiming Technology Streamax Crocus version 1.3.40. It exists in the function queryLast within the endpoint /RepairRecord.do?Action=QueryLast. By manipulating the orderField parameter, an attacker can inject malicious SQL code remotely, potentially compromising the database. The vulnerability is publicly known and exploitable, with proof-of-concept exploits available. [1, 2]
How can this vulnerability impact me? :
This vulnerability can allow attackers to perform unauthorized SQL queries on the affected system, potentially leading to unauthorized data access, data modification, or data loss. Since the Crocus system is used for commercial vehicle safety and fleet management, exploitation could disrupt operations, compromise sensitive data, and impact the integrity and availability of the system. [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 for requests to the endpoint /RepairRecord.do?Action=QueryLast with manipulation of the orderField parameter, which is indicative of SQL injection attempts. Network or web application firewall logs can be inspected for such patterns. Additionally, using tools like sqlmap to test the endpoint for SQL injection is recommended. A sample command to test the vulnerability using sqlmap would be: sqlmap -u "http://<target>/RepairRecord.do?Action=QueryLast&orderField=<injection_payload>" --risk=3 --level=5. Monitoring for unusual or unauthorized access patterns to this endpoint and analyzing logs for suspicious query parameters can also help detect exploitation attempts. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the vulnerable endpoint /RepairRecord.do?Action=QueryLast, especially from untrusted networks. Implement input validation and sanitization on the orderField parameter to prevent SQL injection. Deploy web application firewalls (WAF) with rules to detect and block SQL injection attempts targeting this endpoint. If possible, update or patch the affected software version 1.3.40 once a fix is available. In the meantime, monitor logs for exploitation attempts and consider disabling the vulnerable functionality if it is not critical. [1]