CVE-2026-3969: FeMiner WMS SQL Injection Vulnerability

CVE-2026-3969 Overview

A SQL injection vulnerability has been identified in FeMiner WMS (Warehouse Management System) up to version 1.0. The vulnerability exists in the Basic Organizational Structure Module, specifically within the file /wms-master/src/basic/depart/depart_add_bg.php. An attacker can exploit this flaw by manipulating the Name argument, allowing for SQL injection attacks that can be initiated remotely. The exploit has been publicly disclosed, and the vendor was contacted but did not respond.

Critical Impact
Remote attackers can exploit this SQL injection vulnerability to manipulate database queries, potentially leading to unauthorized data access, data modification, or database compromise without requiring authentication.

Affected Products

FeMiner WMS up to version 1.0
Basic Organizational Structure Module (depart_add_bg.php)

Discovery Timeline

March 12, 2026 - CVE-2026-3969 published to NVD
March 12, 2026 - Last updated in NVD database

Technical Details for CVE-2026-3969

Vulnerability Analysis

This vulnerability is classified as an Injection flaw (CWE-74), specifically manifesting as SQL injection within the FeMiner WMS application. The vulnerable component is located in the department management functionality of the Basic Organizational Structure Module. When processing the Name parameter in depart_add_bg.php, the application fails to properly sanitize or parameterize user-supplied input before incorporating it into SQL queries.

The network-accessible nature of this vulnerability means attackers can exploit it remotely without requiring prior authentication or user interaction. The impact includes potential compromise of data confidentiality, integrity, and availability of the underlying database system.

Root Cause

The root cause of this vulnerability is improper input validation and the lack of parameterized queries in the depart_add_bg.php file. The Name argument is directly concatenated into SQL statements without adequate sanitization, allowing attackers to inject malicious SQL code. This represents a classic SQL injection pattern where user-controlled data is treated as trusted input and incorporated directly into database queries.

Attack Vector

The attack vector is network-based, requiring no authentication or user interaction. An attacker can send specially crafted HTTP requests to the vulnerable endpoint (/wms-master/src/basic/depart/depart_add_bg.php) with malicious SQL payload in the Name parameter. The injected SQL commands are then executed by the database server with the application's privileges.

The vulnerability can be exploited by crafting HTTP requests containing SQL injection payloads in the Name parameter. Attackers may leverage techniques such as UNION-based injection, boolean-based blind injection, or time-based blind injection to extract data or manipulate the database. For technical details, refer to the GitHub Issue Discussion and the VulDB entry.

Detection Methods for CVE-2026-3969

Indicators of Compromise

Unusual SQL error messages in application or web server logs containing syntax errors or unexpected query patterns
HTTP requests to /wms-master/src/basic/depart/depart_add_bg.php with suspicious characters in the Name parameter (e.g., single quotes, UNION, SELECT, OR 1=1)
Database query logs showing malformed or unexpected queries originating from the WMS application
Unexpected database modifications or data exfiltration patterns

Detection Strategies

Deploy Web Application Firewall (WAF) rules to detect and block SQL injection patterns in HTTP requests targeting the vulnerable endpoint
Implement intrusion detection system (IDS) signatures for common SQL injection payloads in POST/GET parameters
Enable verbose logging on the web server and database server to capture suspicious query attempts
Monitor for anomalous database activity including bulk data access or unauthorized schema queries

Monitoring Recommendations

Configure real-time alerting for any requests to depart_add_bg.php containing SQL metacharacters
Establish baseline database query patterns and alert on deviations that may indicate injection attempts
Review web application logs periodically for signs of probing or exploitation attempts against the Basic Organizational Structure Module

How to Mitigate CVE-2026-3969

Immediate Actions Required

If possible, restrict network access to the FeMiner WMS application to trusted IP addresses only
Implement input validation on the Name parameter to allow only expected alphanumeric characters
Deploy WAF rules to block SQL injection attempts targeting the vulnerable endpoint
Consider temporarily disabling the department add functionality until a patch is available

Patch Information

No vendor patch is currently available. The vendor was contacted about this disclosure but did not respond. Organizations using FeMiner WMS should implement the workarounds listed below and monitor for any future security updates from the vendor. For additional details, see the VulDB advisory.

Workarounds

Implement prepared statements or parameterized queries in the depart_add_bg.php file if you have access to modify the source code
Use a Web Application Firewall (WAF) to filter malicious input before it reaches the application
Restrict database user privileges to limit the impact of successful SQL injection attacks
Apply network segmentation to isolate the WMS application from critical systems

bash

# Example: Apache ModSecurity WAF rule to block SQL injection in Name parameter
SecRule ARGS:Name "@detectSQLi" \
    "id:1001,\
    phase:2,\
    deny,\
    status:403,\
    log,\
    msg:'SQL Injection attempt detected in Name parameter',\
    tag:'attack-sqli',\
    severity:'CRITICAL'"