What is the CVSS score of EUVD-2026-29946?

EUVD-2026-29946 has a CVSS 3.1 base score of 6.5 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N. EPSS exploitation probability: 0.0%.

qihang-wms EUVD-2026-29946

| CVE-2026-37428 MEDIUM

SQL Injection (CWE-89)

2026-05-13 mitre

GHSA-pj9f-375x-gx35

SQLi N A

6.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

6.5 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Jun 08, 2026 - 10:50 vuln.today

CVSS changed

May 13, 2026 - 19:22 NVD

6.5 (MEDIUM)

CVE Published

May 13, 2026 - 00:00 nvd

UNKNOWN (no severity yet)

DescriptionCVE.org

qihang-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).

AnalysisAI

SQL injection in qihang-wms (commit 75c15a) via the unsanitized datascope parameter in SysDeptMapper.xml allows remote database access without authentication. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms unauthenticated, network-accessible, low-complexity exploitation yielding partial confidentiality and integrity impact, including exposure of users' PII from the backend database. Publicly available exploit code exists via GitHub-hosted writeups and proof-of-concept scripts, though EPSS sits at 0.03% (9th percentile) and SSVC reports no confirmed active exploitation at time of analysis.

Technical ContextAI

qihang-wms (启航电商WMS) is a Chinese-language warehouse management system built on a Java stack with MyBatis as its ORM layer. MyBatis defines SQL queries in XML mapper files; when developers use the ${param} interpolation syntax instead of the safe #{param} parameterized syntax, user-supplied input is concatenated directly into the SQL string. The datascope parameter in SysDeptMapper.xml is the specific injection point, likely used to filter department-scope queries dynamically. CWE-89 (Improper Neutralization of Special Elements in SQL Commands) is the root cause class. No formal CPE entry exists (listed as cpe:2.3:a:n/a:n/a), and affected version data is tied solely to commit 75c15a of the qihang-wms repository with no broader version range confirmed by available intelligence.

RemediationAI

No vendor-released patch has been identified at time of analysis; the fix status for qihang-wms beyond commit 75c15a is unconfirmed. The primary code-level fix is to replace string-concatenated SQL in SysDeptMapper.xml with MyBatis parameterized syntax - specifically, changing ${datascope} references to #{datascope}, which causes MyBatis to use prepared statements and prevents injection. As a compensating control, implement strict input allowlisting for the datascope parameter at the application layer, restricting it to expected enumerated values (e.g., department ID integers), which will break injection payloads but may affect legitimate functionality if the parameter accepts arbitrary scope expressions. Deploying a WAF with SQL injection detection rules targeting the vulnerable endpoint provides an additional layer but is not a substitute for code fixes and may generate false positives on legitimate queries containing SQL-like terms. Restrict network access to qihang-wms to internal networks only if internet exposure is not required. The researcher's technical writeup is available at https://github.com/Y4y17/CVE/blob/main/%E5%90%AF%E8%88%AA%E7%94%B5%E5%95%86WMS/SQL%20injection%20vulnerability-1.md and additional POC material at https://gist.github.com/Y4y17/6587147a37eba5b31de832e067f317ef.