dbcve.org
InjectionWeakness · CWE-74

CVE-2026-3969

HIGH · 7.3 CVSS v3.1 Published 2026-03-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 vulnerability was detected in FeMiner wms up to 1.0. This impacts an unknown function of the file /wms-master/src/basic/depart/depart_add_bg.php of the component Basic Organizational Structure Module. Performing a manipulation of the argument Name results in sql injection. The attack may be initiated remotely. The exploit is now public and may be used. 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 version 1.0 allows remote attackers to inject malicious SQL queries via the Name parameter in /wms-master/src/basic/depart/depart_add_bg.php within the Basic Organizational Structure Module. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries.

MitigationReplace dynamic SQL queries with parameterized queries or prepared statements. Implement input validation on all user-supplied parameters, especially the Name argument. Conduct a full audit of the application for additional SQL injection vulnerabilities.

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

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
Low
Integrity
Low
Availability
Low

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

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 and version
    Locate the FeMiner WMS application directory and check for version files, headers, or metadata that identify the installed version. Compare against version 1.0.
    Affected if The installed version is FeMiner WMS version 1.0 or falls within the affected version range.
  2. Verify vulnerable file exists
    Inspect the application directory for the presence of /wms-master/src/basic/depart/depart_add_bg.php as referenced in the CVE.
    Affected if The file depart_add_bg.php exists in the /wms-master/src/basic/depart/ directory.
  3. Check if Basic Organizational Structure Module is enabled
    Verify that the Basic Organizational Structure Module is accessible and functional within the WMS application.
    Affected if The Basic Organizational Structure Module is deployed and accessible to users.
  4. Identify Name parameter exposure
    Locate forms or API endpoints within the Basic Organizational Structure Module that accept a Name parameter and submit data to depart_add_bg.php.
    Affected if The Name parameter in depart_add_bg.php accepts user input without visible sanitization or parameterized query usage in the code.
  5. Review database query implementation
    Examine the source code of depart_add_bg.php to determine if dynamic SQL queries are used with the Name parameter instead of prepared statements or parameterized queries.
    Affected if The code constructs SQL queries by directly concatenating or inserting the Name parameter into the query string without using parameterized queries or input sanitization.

A user is affected if FeMiner WMS version 1.0 is installed with the Basic Organizational Structure Module enabled, where the depart_add_bg.php file processes the Name parameter using dynamic SQL queries without parameterized statements.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries or prepared statements. Implement input validation on all user-supplied parameters, especially the Name argument. Conduct a full audit of the application for additional SQL injection vulnerabilities.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3969 — 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-3969 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