dbcve.org
Warehouse Management SystemApplication · Feminer

CVE-2026-1059

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-17
Fix available
A fix is available. Upgrade to after 2021-11-15 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in FeMiner WMS /src/chkuser.php via the Username parameter allows remote attackers to inject malicious SQL queries. The vulnerability has a critical CVSS score of 9.8 and a public exploit is available.

MitigationImplement parameterized queries (prepared statements) in chkuser.php to neutralize the SQL injection. Until the fix is deployed, consider deploying a WAF rule to block SQL injection attempts targeting the Username parameter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Warehouse Management SystemApplication
Affected:<= 2021-11-15

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm FeMiner WMS installation
    Locate the FeMiner WMS web application directory on the server. Check for the presence of typical WMS file structures or check web server configuration for FeMiner WMS virtual hosts/paths.
    Affected if FeMiner WMS is present on the server
  2. Verify vulnerable file exists
    Inspect the application directory for the file /src/chkuser.php. This is the specific file containing the SQL injection vulnerability.
    Affected if The file /src/chkuser.php exists in the application root
  3. Check Username parameter handling
    Review the source code of /src/chkuser.php and locate the handling of the Username parameter. Look for direct string concatenation in SQL queries without parameterized queries or input sanitization.
    Affected if The Username parameter is used directly in SQL queries without prepared statements or proper escaping
  4. Determine installed version
    Check for version information in application files such as version.php, README files, or configuration files. Compare against the affected version range (all versions <= 2021-11-15).
    Affected if The installed version is FeMiner WMS dated 2021-11-15 or earlier, or the version cannot be determined
  5. Assess network exposure
    Verify if the FeMiner WMS application is accessible over the network. Check firewall rules and web server access controls to determine if the /src/chkuser.php endpoint is reachable from external sources.
    Affected if The vulnerable endpoint is accessible remotely without authentication

The environment is affected if FeMiner WMS is installed, the file /src/chkuser.php exists with direct SQL query construction using the Username parameter, and the application is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 2021-11-15
Interim mitigation

Implement parameterized queries (prepared statements) in chkuser.php to neutralize the SQL injection. Until the fix is deployed, consider deploying a WAF rule to block SQL injection attempts targeting the Username parameter.

Fix this in Warehouse Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1059 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1059 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data