CVE-2026-37429
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 · uneditedqihang-wms commit 75c15a was discovered to contain a SQL injection vulnerability via the datascope parameter in the SysUserMapper.xml file. This vulnerability allows attackers to access sensitive database information, including users' Personally Identifiable Information (PII) via a crafted SQL statement.
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 · moderate confidenceSQL injection vulnerability in qihang-wms allows remote attackers to inject malicious SQL statements through the datascope parameter in SysUserMapper.xml, enabling unauthorized access to sensitive database contents including user PII.
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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm qihang-wms installationLocate the qihang-wms application in your environment and identify its installation directory. Search for the presence of SysUserMapper.xml file, typically found in the mapper or mybatis mapping directory.Affected if qihang-wms is deployed and SysUserMapper.xml exists in the application
-
Locate SysUserMapper.xmlSearch for SysUserMapper.xml in the application's source code or deployment artifacts. This file is typically located in a mybatis mapper directory.Affected if SysUserMapper.xml file is found in the application
-
Examine datascope parameter usageOpen SysUserMapper.xml and search for any usage of the 'datascope' parameter. Inspect how it is used in SQL queries - look for ${datascope} syntax (dynamic SQL) vs #{datascope} (parameterized).Affected if The datascope parameter is used with ${datascope} syntax allowing direct string substitution
-
Verify if user input reaches the datascope parameterTrace the code flow from HTTP request parameters to the MyBatis mapper call. Check if the datascope parameter is directly populated from user input without validation or parameterization.Affected if User-supplied input flows directly into the datascope parameter without sanitization or use of MyBatis #{} binding
-
Identify exposure to remote attackersDetermine if the affected endpoint is accessible over the network without authentication or with standard authentication, allowing remote attackers to supply malicious datascope values.Affected if The SQL query using datascope is accessible to unauthenticated or authenticated remote users
You are affected if qihang-wms is deployed and SysUserMapper.xml contains dynamic SQL using ${datascope} that accepts direct user input.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace dynamic SQL in SysUserMapper.xml with parameterized queries or MyBatis #{} syntax, audit other mapper files for similar injection patterns, and implement input validation on the datascope parameter.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-37429 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-37429 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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