Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-1059: SQL Injection in FeMiner wms

0
Medium
VulnerabilityCVE-2026-1059cvecve-2026-1059
Published: Sat Jan 17 2026 (01/17/2026, 18:32:06 UTC)
Source: CVE Database V5
Vendor/Project: FeMiner
Product: wms

Description

A security vulnerability has been detected in FeMiner wms up to 9cad1f1b179a98b9547fd003c23b07c7594775fa. Affected by this vulnerability is an unknown functionality of the file /src/chkuser.php. The manipulation of the argument Username leads to sql injection. The attack is possible to be carried out remotely. The exploit has been disclosed publicly and may be used. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified. The vendor was contacted early about this disclosure but did not respond in any way.

AI-Powered Analysis

AILast updated: 01/25/2026, 19:36:55 UTC

Technical Analysis

CVE-2026-1059 identifies a SQL injection vulnerability in the FeMiner wms product, specifically in the /src/chkuser.php file where the Username parameter is improperly sanitized. This flaw allows an unauthenticated remote attacker to inject malicious SQL code, potentially enabling unauthorized data retrieval, modification, or deletion within the backend database. The vulnerability is exploitable without any user interaction, making it highly accessible to attackers scanning for vulnerable instances. FeMiner wms employs a rolling release model, which means affected versions cannot be precisely enumerated, complicating patch management and vulnerability tracking. The vendor was contacted but did not respond, and no official patches or updates have been released. Although public exploit code has been disclosed, there are no confirmed reports of active exploitation in the wild. The CVSS 4.0 base score is 6.9 (medium severity), reflecting the network attack vector, low attack complexity, and no required privileges or user interaction, but limited impact on confidentiality, integrity, and availability. The vulnerability poses a significant risk to organizations relying on FeMiner wms for warehouse management or related operations, as attackers could leverage this flaw to compromise sensitive data or disrupt services.

Potential Impact

For European organizations, this vulnerability could lead to unauthorized access to sensitive operational or customer data managed within FeMiner wms databases, potentially violating GDPR and other data protection regulations. Integrity of critical warehouse management data could be compromised, leading to operational disruptions, inventory inaccuracies, or financial losses. Availability could also be impacted if attackers execute destructive SQL commands or cause database outages. The lack of vendor response and patches increases the risk exposure period. Organizations in sectors such as manufacturing, logistics, and retail that depend on FeMiner wms are particularly vulnerable. Additionally, the public disclosure of exploit code raises the likelihood of opportunistic attacks targeting European entities. The medium severity rating suggests a moderate but tangible threat that should be addressed promptly to avoid escalation or chaining with other vulnerabilities.

Mitigation Recommendations

Given the absence of official patches, European organizations should implement immediate compensating controls. First, apply strict input validation and sanitization on all user-supplied data, especially the Username parameter in /src/chkuser.php, to block SQL injection payloads. Deploy Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting FeMiner wms. Conduct thorough code reviews and security testing of the affected component to identify and remediate injection points. Restrict network access to the application to trusted IP ranges and monitor logs for suspicious queries or failed login attempts. Consider isolating the database with least privilege principles to limit damage if exploitation occurs. Maintain heightened monitoring for indicators of compromise and prepare incident response plans. Engage with the vendor or community for updates and patches, and plan for rapid deployment once available. Finally, educate development and operations teams about secure coding practices and the risks of SQL injection.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2026-01-16T19:04:21.251Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 696c87f2d302b072d9a7fc74

Added to database: 1/18/2026, 7:12:50 AM

Last enriched: 1/25/2026, 7:36:55 PM

Last updated: 2/7/2026, 9:57:50 AM

Views: 71

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats