CVE-2025-8126
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-8126 is a critical SQL injection vulnerability in the deerwms deer-wms-2 Warehouse Management System versions up to 3.3. It occurs in the /system/user/export endpoint where the user-controllable parameter params[dataScope] is not properly sanitized or parameterized. This allows attackers to inject malicious SQL code directly into the database query, enabling them to extract sensitive information or execute arbitrary SQL commands. The vulnerability can be exploited remotely without authentication, and a public proof-of-concept exploit is available. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized extraction of sensitive data from the database, manipulation of data integrity, and potentially full control over the affected server. Attackers can remotely exploit this flaw to execute arbitrary SQL commands, leading to confidentiality, integrity, and availability breaches of the system. Since no known mitigations exist, the affected system is highly vulnerable to compromise. [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/user/export endpoint with malicious payloads in the params[dataScope] parameter to test for SQL injection. For example, you can use curl to send a test payload that attempts to extract database information, such as: curl -X POST 'http://<target>/system/user/export' -d 'params[dataScope]=and extractvalue(1,concat(0x7e,(select database()),0x7e))' If the response contains database information or an error related to SQL functions, it indicates the presence of the vulnerability. Network intrusion detection systems can also be configured to detect such suspicious payloads targeting this endpoint. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include disabling or restricting access to the /system/user/export endpoint to prevent exploitation, especially from untrusted networks. Since no known countermeasures or patches are documented, consider replacing the affected deer-wms-2 software version (up to 3.3) with a secure alternative or updated version once available. Additionally, monitor network traffic for exploitation attempts and apply web application firewall (WAF) rules to block malicious SQL injection payloads targeting the params[dataScope] parameter. [2]