CVE-2025-8163
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 |
|---|---|---|
| deerwms | deer-wms-2 | to 3.3 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-8163 is a critical SQL injection vulnerability in the deerwms deer-wms-2 Warehouse Management System versions up to 3.3. It occurs because the parameter params[dataScope], passed to the /system/role/list endpoint, is not properly sanitized and is directly inserted into an SQL query without using prepared statements. This allows an attacker to inject malicious SQL code remotely, potentially extracting sensitive data or gaining full control over the affected server. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized extraction of sensitive data from the database, compromise of data confidentiality, integrity, and availability, and potentially allow attackers to gain full control over the server hosting the application. Since the vulnerability can be exploited remotely without authentication and a proof-of-concept exploit is publicly available, the risk of attack is significant. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending crafted HTTP POST requests to the /system/role/list endpoint with malicious payloads in the params[dataScope] parameter to test for SQL injection. For example, you can use curl to send a request like: curl -X POST -d 'params[dataScope]=and extractvalue(1,concat(0x7e,(select database()),0x7e))' http://<target>/system/role/list and observe if the response reveals database errors or unexpected data, indicating SQL injection. Monitoring network traffic for unusual POST requests to /system/role/list with suspicious params[dataScope] values can also help detect exploitation attempts. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting or blocking access to the /system/role/list endpoint to prevent exploitation, applying input validation and sanitization on the params[dataScope] parameter, and using prepared statements or parameterized queries in the application code to prevent SQL injection. Since no official patches or mitigations are reported, consider replacing or upgrading the affected software if possible. Additionally, monitor for exploitation attempts and apply network-level protections such as web application firewalls to block malicious payloads targeting this vulnerability. [2, 3]