Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege app account
-
DeliveryReach Inbound QC PDA list endpoint
-
ExploitInject SQL via searchstr parameter
-
ExecutionDatabase executes crafted query
-
ImpactExfiltrate or tamper with stored data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Input neutralization, injection prevention
|
| Exploitation Conditions | Requires an authenticated low-privilege account (CVSS PR:L) with access to the Inbound Quality Check PDA interface; the attacker must be able to reach the WmInQmIController.list endpoint and supply the 'searchstr' request parameter, which is passed into a SQL query without sanitization. No user interaction is needed (UI:N) and no special non-default configuration is indicated. The primary limiting factor is the authentication requirement - this is NOT exploitable by fully unauthenticated attackers - which, combined with the product's niche deployment, meaningfully constrains real-world exploitation. |
| Impact | This is a LOW real-world priority despite being a remotely reachable SQL injection. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) confirms network-reachable, low-complexity exploitation, but PR:L means a valid authenticated account is required - this is not an unauthenticated flaw. The vendor-assigned base score of 2.1 reflects only partial impacts (VC:L/VI:L/VA:L), a conservative VulDB rating that undersells typical SQLi potential; a single injection point can often be leveraged for broader database read/write than 'Low' implies, so defenders should treat the impact ceiling with some skepticism. Exploitation signals are mixed-to-weak: a public exploit exists (E:P in the vector), but there is NO CISA KEV listing and NO EPSS score was provided, so there is no evidence of active or widespread exploitation. The vulnerability is sourced solely from VulDB (CNA cna@vuldb.com) with no independent NVD enrichment, no vendor advisory, and no patch - the vendor was contacted but did not respond, meaning no official fix exists. Net: a genuine but authentication-gated bug in a niche product, worth patching/mitigating where JEEWMS is deployed, but not a broad emergency. |
| Exploit ScenarioDerived | An attacker who holds (or obtains) low-privilege authenticated access to a JEEWMS instance submits a crafted value in the 'searchstr' parameter of the Inbound Quality Check PDA list endpoint, injecting SQL that the WmInQmIController.list function passes unsanitized into a database query. A public proof-of-concept exists, lowering the skill barrier, allowing extraction or manipulation of backend database contents. Because the attack vector is network-based with low complexity, it can be performed remotely over the application's normal web interface. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
SQL injection in the JEEWMS warehouse management system (erzhongxmu JEEWMS through build 2026.09.27-W39) lets an authenticated low-privilege user execute arbitrary SQL by manipulating the 'searchstr' argument handled by WmInQmIController.list in the Inbound Quality Check PDA interface. The vulnerability is remotely reachable (CVSS:4.0 base 2.1; assessed CVSS:3.1 6.3, AV:N/AC:L/PR:L/UI:N with low confidentiality, integrity and availability impact), so the primary constraint on exploitation is that the attacker needs a valid low-privilege account - it is not exploitable by fully unauthenticated parties. Publicly available exploit code exists and the vendor was contacted but never responded, so no vendor patch is currently identified; the issue is not in CISA KEV and real-world priority is low given the authentication prerequisite and the niche deployment footprint of this product.
RemediationAI
No vendor-released patch was identified at the time of analysis - the vendor was contacted early and did not respond - so remediation must rely on source-level fixes and compensating controls. The most effective fix is to rewrite WmInQmIController.list so the 'searchstr' value is passed through parameterized/prepared statements or a safe ORM query instead of being concatenated into SQL; any team running a forked or internally maintained JEEWMS build should apply this change directly, as the change is localized to a single controller method and carries little regression risk. Until then, restrict the Inbound Quality Check PDA interface (and the WmInQmIController endpoints generally) to trusted internal networks or VPN, or enable it only for the specific PDA clients and IP ranges that need it, accepting the trade-off that off-site or roaming PDA users lose access. Ensure the database account used by JEEWMS has least privilege - read/write on the JEEWMS schema only, no administrative rights - so successful injection cannot escalate beyond that schema. Deploy WAF or IPS rules that block SQL metacharacters and common injection patterns on requests to the PDA endpoints; recognize that this is signature-based and can be bypassed with encoding tricks, so it should be treated as defense in depth rather than a fix. Monitor database and application logs for anomalous SQL errors or unusual query behavior from the WmInQmIController.list path, and review the referenced VulDB entries (https://vuldb.com/vuln/416558/cti) for updated indicators or an eventual vendor fix.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is the Inbound Quality Check PDA interface of JEEWMS, a Java/Spring-based open-source warehouse management system. The vulnerable function is WmInQmIController.list in src/main/java/com/zzjee/wm/controller/WmInQmIController.java; the request parameter 'searchstr' is concatenated into a SQL statement rather than being bound as a parameter, so the input is interpreted as SQL by the underlying relational database. This is an injection flaw (CWE-74 broadly, with CWE-89 SQL injection as the concrete root-cause class): the application fails to neutralize special elements in externally supplied data before it reaches the database interpreter, allowing an attacker to alter query structure and read or modify data within the database account's privileges. Because the sink is an HTTP-exposed Spring controller in a PDA-facing endpoint, the injection is triggerable over the network with only a low-privileged session, consistent with the assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L vector. No non-default configuration is required, and the impact stays scoped to the application's own database context (S:U, scope unchanged).
Know when Java gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
Network-reachable, low-complexity SQLi requiring an authenticated account (PR:L), no user interaction; partial database confidentiality/integrity/availability impact consistent with VulDB's low rating.
Primary rating from Vendor (vuldb).
CVSS VectorVendor: vuldb
DescriptionCVE.org
A vulnerability was determined in erzhongxmu JEEWMS up to 2026.09.27-W39. This impacts the function WmInQmIController.list of the file src/main/java/com/zzjee/wm/controller/WmInQmIController.java of the component Inbound Quality Check Pda Interface. This manipulation of the argument searchstr causes sql injection. The attack is possible to be carried out remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
Related Vulnerabilities in JEEWMS SQL Injection and Injection Flaws
View all 4Oracle Java SE 7 Update 6 and earlier contains multiple sandbox bypass vulnerabilities via the ClassFinder and forName m
Remote code execution in IBM Sterling B2B Integrator, Sterling Integrator, and Tivoli Common Reporting allows unauthenti
Java Runtime Environment sandbox bypass via incorrect image channel verification in 2D component allows remote unauthent
Oracle Java SE JDK/JRE 7 and 6 Update 27 and earlier allows remote code execution with complete system compromise throug
JBoss Seam 2 in Red Hat JBoss EAP 4.3.0 fails to sanitize JBoss Expression Language inputs, allowing remote attackers to
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 update 4 and earlier, 6 up
Multiple vulnerabilities in Oracle Java 7 before Update 11 allow remote attackers to execute arbitrary code by (1) using
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 2 and earlier, 6 Up
The WLS Security component in Oracle WebLogic Server 10.3.6.0, 12.1.2.0, 12.1.3.0, and 12.2.1.0 allows remote attackers
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 7 and earlier allow
Remote unauthenticated attackers can execute arbitrary code on Adobe ColdFusion servers through Java deserialization fla
The ExceptionDelegator component in Apache Struts before 2.2.3.1 interprets parameter values as OGNL expressions during
EUVD-2026-97133
GHSA-rr5m-w4c2-x5h4
NVD
CVE.org
EPSS
VulDB
Exploit-DB