CVE-2025-8127

6.3 MEDIUM

📋 TL;DR

A critical SQL injection vulnerability in deerwms deer-wms-2 allows remote attackers to execute arbitrary SQL commands via the params[dataScope] parameter in the /system/user/list endpoint. This affects all versions up to 3.3, potentially compromising database confidentiality, integrity, and availability. Organizations using vulnerable versions of this warehouse management system are at risk.

💻 Affected Systems

Products:
  • deerwms deer-wms-2
Versions: up to 3.3
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: All deployments using affected versions are vulnerable if the /system/user/list endpoint is accessible.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, data manipulation, privilege escalation, and potential remote code execution through database functions.

🟠

Likely Case

Unauthorized data access and extraction of sensitive information from the database, potentially including user credentials and business data.

🟢

If Mitigated

Limited impact with proper input validation and parameterized queries preventing successful exploitation.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploit details have been publicly disclosed, making weaponization likely. The vulnerability requires authentication to the system.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://gitee.com/deerwms/deer-wms-2/issues/ICLQT8

Restart Required: No

Instructions:

1. Monitor the vendor's repository for security updates. 2. Apply any available patches immediately. 3. Consider upgrading to version 3.4 or later if available.

🔧 Temporary Workarounds

Input Validation Filter

all

Implement server-side input validation to sanitize the params[dataScope] parameter

# Add input validation in the affected endpoint handler

WAF Rule Implementation

all

Deploy web application firewall rules to block SQL injection patterns

# Configure WAF to block SQL injection patterns in POST parameters

🧯 If You Can't Patch

  • Implement network segmentation to restrict access to the vulnerable endpoint
  • Deploy database monitoring to detect unusual SQL queries and access patterns

🔍 How to Verify

Check if Vulnerable:

Check if the system version is 3.3 or earlier and if the /system/user/list endpoint accepts params[dataScope] parameter

Check Version:

Check application version in admin panel or configuration files

Verify Fix Applied:

Test the vulnerable endpoint with SQL injection payloads to confirm they are properly sanitized or blocked

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in application logs
  • Multiple failed authentication attempts followed by SQL injection patterns
  • Unexpected database errors in logs

Network Indicators:

  • HTTP POST requests to /system/user/list with SQL keywords in parameters
  • Unusual database connection patterns from application servers

SIEM Query:

source="application.logs" AND ("params[dataScope]" AND ("SELECT", "UNION", "OR", "--"))

🔗 References

📤 Share & Export