CVE-2026-1059VulnerabilityPublished 17 Jan 2026Updated 23 Feb 2026

CVE-2026-1059: FeMiner wms · SQL Injection

Affects FeMiner wmsSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
FeMinerwms	Affected =9cad1f1b179a98b9547fd003c23b07c7594775fa	Fixed in–

AI-suggested

Organizations should immediately audit their use of FeMiner wms and identify instances running affected versions. As no official patches are available, implement web application firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the Username parameter in /src/chkuser.php. Employ input validation and parameterized queries at the application level if source code access is possible to sanitize user inputs. Monitor logs for suspicious database query patterns and failed login attempts indicative of injection attempts. Restrict network access to the wms application to trusted IP ranges and enforce strict access controls. Conduct regular security assessments and penetration tests focusing on injection flaws. Prepare incident response plans for potential data breaches or service disruptions. Engage with the vendor for updates and consider alternative solutions if remediation is delayed. Finally, keep backups of critical data to enable recovery in case of data corruption or loss.

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.

Impact

The SQL injection vulnerability in FeMiner wms can lead to unauthorized access to sensitive data, including user credentials and operational information, potentially resulting in data breaches. Attackers could manipulate database queries to alter or delete data, disrupting warehouse management processes and causing operational downtime. The integrity of business-critical data could be compromised, leading to incorrect inventory records or shipment errors. Availability may also be affected if attackers execute denial-of-service conditions through crafted SQL payloads. Given the remote, unauthenticated nature of the exploit, the threat surface is broad, increasing the likelihood of exploitation. Organizations in logistics, manufacturing, and retail sectors using FeMiner wms could face financial losses, reputational damage, and regulatory penalties if exploited. The lack of vendor response and patches exacerbates the risk, leaving systems exposed until mitigations are applied.

Summary

CVE-2026-1059 identifies a SQL injection vulnerability in FeMiner wms, an application used for warehouse management. The vulnerability resides in the /src/chkuser.php file, where the Username parameter is improperly sanitized, allowing an attacker to inject malicious SQL queries. This injection flaw can be exploited remotely without requiring authentication or user interaction, making it highly accessible to attackers. The product uses a rolling release strategy, complicating exact version identification, but all versions up to the specified commit hash are affected. The vulnerability has a CVSS 4.0 base score of 6.9, indicating medium severity, with network attack vector, low complexity, and no privileges or user interaction required. The impact includes potential unauthorized data access, modification, or deletion, which could compromise system integrity and availability. The vendor was notified but has not issued a patch or response, and no known exploits are currently active in the wild, though public exploit code exists. This vulnerability poses a significant risk to organizations relying on FeMiner wms for critical warehouse management operations, especially where sensitive or regulated data is stored.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 22:47 UTC

Technical details

References

Community reviews

Related threats