CVE-2025-8773
BaseFortify
Publication date: 2025-08-09
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 |
|---|---|---|
| dahuatech | monitoring_platform | 1.0 |
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-8773 is a critical SQL injection vulnerability in the Dinstar Monitoring Platform version 1.0. It exists in the file /itc/${appPath}/login_getPasswordErrorNum.action, specifically in the handling of the userBean.loginName parameter. Improper input sanitization allows an attacker to inject malicious SQL code remotely without authentication, potentially compromising the system's confidentiality, integrity, and availability. [1, 2]
How can this vulnerability impact me? :
Exploitation of this vulnerability can allow attackers to execute arbitrary SQL commands on the affected system remotely without authentication. This can lead to unauthorized access, data leakage, modification or deletion of data, and potentially gaining server privileges, severely impacting the confidentiality, 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 testing the /itc/${appPath}/login_getPasswordErrorNum.action endpoint for SQL injection via the userBean.loginName parameter. You can use tools like curl or sqlmap to send crafted payloads to this parameter and observe if SQL errors or unexpected behavior occur. For example, using curl: curl -X POST 'http://target/itc/${appPath}/login_getPasswordErrorNum.action' -d 'userBean.loginName=admin' and then with a SQL injection payload such as 'admin' OR '1'='1'. Alternatively, sqlmap can be used to automate detection: sqlmap -u 'http://target/itc/${appPath}/login_getPasswordErrorNum.action' --data='userBean.loginName=admin' --risk=3 --level=5. Monitoring network traffic for suspicious SQL injection patterns targeting this endpoint can also help detect exploitation attempts. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include disabling or restricting access to the vulnerable /itc/${appPath}/login_getPasswordErrorNum.action endpoint to prevent remote exploitation. Since no official patches or vendor responses are available, consider implementing web application firewall (WAF) rules to block SQL injection attempts targeting the userBean.loginName parameter. Additionally, monitor logs for suspicious activity and consider replacing the affected product with a secure alternative. Avoid exposing the vulnerable service to untrusted networks until a fix is available. [1]