CVE-2026-37428
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 SysDeptMapper.xml file. This vulnerability allows attackers to access sensitive database information, including users' Personally Identifiable Information (PII).
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 confidenceA SQL injection vulnerability exists in qihang-wms (commit 75c15a) via the datascope parameter in SysDeptMapper.xml. Attackers can exploit this flaw to inject malicious SQL queries and exfiltrate sensitive data including personally identifiable information (PII) from the database.
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.
-
Locate qihang-wms installationSearch for the qihang-wms application directory or check for SysDeptMapper.xml file in the project codebaseAffected if qihang-wms is present and uses the affected SysDeptMapper.xml file
-
Identify the vulnerable fileLocate SysDeptMapper.xml in the mapper directory (typically in src/main/resources/mapper/ or similar) and verify it contains a datascope parameterAffected if The file exists and contains datascope parameter usage
-
Check for vulnerable SQL syntaxOpen SysDeptMapper.xml and search for the datascope parameter usage - look for dynamic SQL concatenation patterns like ${datascope} instead of #{datascope}Affected if The datascope parameter is used with ${} (dollar sign) syntax instead of #{} syntax, indicating dynamic SQL concatenation
-
Verify the query contextExamine the SQL query containing datascope - check if it builds a WHERE clause or condition using string concatenationAffected if The datascope parameter is directly concatenated into SQL strings without parameterization
-
Confirm database exposureReview application logs or database access patterns for the SysDeptMapper queries - test if unsanitized input in datascope can alter query behaviorAffected if User-controlled input can be passed to the datascope parameter without validation or parameterization
A user is affected if qihang-wms is deployed with SysDeptMapper.xml using ${datascope} dynamic SQL concatenation instead of parameterized #{datascope} queries.
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 concatenation in the datascope parameter with parameterized queries or MyBatis #{} syntax to prevent SQL injection. If a patched version is available, upgrade to that version.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-37428 — 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-37428 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