Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege JEEWMS account
-
DeliverySend crafted autocomplete request
-
ExploitInject SQL via trem/searchField/entityName
-
ExecutionBackend executes malicious query
-
ImpactExtract database contents
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated session with at least low-level privileges (PR:L) to reach the Autocomplete Handler, then manipulation of the trem, searchField, or entityName arguments passed to CommonServiceImpl.getAutoList. No user interaction is needed and the endpoint is reachable over the network. Limiting factors: the attacker must hold valid application credentials (not unauthenticated), the affected product (erzhongxmu JEEWMS, versions up to 2026.09.27-W39) has a narrow deployment base, and no vendor fix exists - so mitigation depends on restricting account access, input validation, or network exposure rather than patching. |
| Impact | This is a CWE-89 SQL injection in the Autocomplete Handler (CommonServiceImpl.getAutoList) of JEEWMS, an open-source Java warehouse management system. The provided CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) indicates network-reachable, low-complexity exploitation requiring authenticated low privileges (PR:L), with Exploit maturity E:P (proof-of-concept). The vendor-assigned base score is 5.3 (Medium), tempered by the fact that each impact metric is rated Low (VC:L/VI:L/VA:L). This impact rating appears conservative for SQL injection, which commonly permits broad database read/extraction - the real confidentiality impact may be understated, so this should be treated as a genuine data-exposure risk rather than dismissed on the 5.3 score alone. Countervailing the severity: a VulDB-provided public exploit exists (POC), but there is NO CISA KEV listing and NO EPSS score in the input, so there is no evidence of widespread or active exploitation - publicly available exploit code is a distinct and lower signal than confirmed in-the-wild use. The PR:L requirement is a meaningful limiter: an attacker needs valid (even low-level) application credentials. Net: a credible, patch-worthy priority for anyone running JEEWMS with untrusted authenticated users, but not an emergency-grade internet-wide threat given the niche product footprint and lack of KEV/EPSS corroboration. |
| Exploit ScenarioDerived | An authenticated low-privilege user sends a crafted request to the JEEWMS autocomplete endpoint, manipulating the trem, searchField, or entityName parameters consumed by CommonServiceImpl.getAutoList, injecting SQL that the backend executes against the database. Because a public proof-of-concept exploit has been released, an attacker with any valid account could reuse it to enumerate and extract database contents (e.g., user records or credentials) remotely over the network. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
SQL injection in the Autocomplete Handler of erzhongxmu JEEWMS (versions up to 2026.09.27-W39) allows remote attackers who already hold a valid low-privilege account to manipulate the trem, searchField, or entityName arguments passed to CommonServiceImpl.getAutoList and execute arbitrary SQL against the backend database, exposing data reachable by that account. Publicly available exploit code exists, so the attack is practical for any user able to authenticate and reach the endpoint; the vector's E:P rating and the reporter's note that the exploit was made public confirm exploitability, though there is no CISA KEV listing indicating confirmed active exploitation. The vendor was contacted early but never responded, and no vendor-released patched version has been identified.
RemediationAI
No vendor-released patch has been identified at the time of analysis: the maintainer was contacted early about the disclosure and did not respond, and the wildcard CPE shows no fixed build, so teams must rely on compensating controls. Because exploitation requires an authenticated low-privilege session (PR:L), the highest-value immediate step is to restrict the Autocomplete Handler endpoint to trusted accounts only, remove or disable unused/low-privilege accounts, and place the application behind network controls so only known users can reach it. Where the code is maintained in-house, modify CommonServiceImpl.getAutoList to use parameterized queries or JPA Criteria bindings and replace client-supplied searchField/entityName values with a hard-coded server-side allowlist of permitted column and entity names; this may reduce autocomplete flexibility for non-whitelisted fields but eliminates the injection path. As a temporary measure, a WAF or reverse-proxy rule that rejects SQL metacharacters and keywords in the trem, searchField and entityName parameters blocks common payloads, though it can cause false positives on legitimate search strings containing quotes or hyphens and is easily bypassed by encoding tricks. Disabling the autocomplete feature entirely is the most reliable short-term mitigation if the business can absorb the usability loss. Monitor database and application logs for anomalous autocomplete queries. Advisory references: https://vuldb.com/vuln/416561, https://vuldb.com/vuln/416561/cti, https://vuldb.com/cve/CVE-2026-108782.
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
JEEWMS is an open-source Java warehouse management system built on the Jeecg rapid-development framework, which uses Spring MVC, Hibernate/JDBC and dynamic query builders. The flaw is CWE-89 (Improper Neutralization of Special Elements used in an SQL Command) in the Autocomplete Handler's CommonServiceImpl.getAutoList method (src/main/java/org/jeecgframework/core/common/service/impl/CommonServiceImpl.java), where user-supplied request parameters named trem, searchField and entityName are concatenated into SQL rather than bound as parameters or validated against a server-side allowlist of column/entity names. Because searchField and entityName normally select which column and entity an autocomplete dropdown queries, they are especially dangerous injection points. The CPE cpe:2.3:a:erzhongxmu:jeewms:*:*:*:*:*:*:*:* uses a wildcard version range, indicating every release through the 2026.09.27-W39 build is considered affected and no fixed build is enumerated. Our independent assessment scores the issue CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N: network reachable, low-complexity, requires authentication, no user interaction, and results primarily in high confidentiality impact rather than integrity or availability loss, which should guide triage away from assumptions of full database takeover or data destruction.
Know when Jeewms 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 authenticated SQLi (PR:L) in a read-oriented autocomplete query enables broad database extraction, so C:H; no clear write/availability impact, so I:N/A:N.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
2DescriptionCVE.org
A weakness has been identified in erzhongxmu JEEWMS up to 2026.09.27-W39. Affected by this issue is the function CommonServiceImpl.getAutoList of the file src/main/java/org/jeecgframework/core/common/service/impl/CommonServiceImpl.java of the component Autocomplete Handler. Executing a manipulation of the argument trem/searchField/entityName can lead to sql injection. It is possible to launch the attack remotely. The exploit has been made available to the public and could be used for attacks. 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 4An issue in Jeewms v.3.7 and before allows a remote attacker to escalate privileges via the AuthInterceptor component. R
Directory Traversal vulnerability in Jeewms v.3.7 and before allows a remote attacker to obtain sensitive information vi
A vulnerability was found in Guangzhou Huayi Intelligent Technology Jeewms 3.7. Rated medium severity (CVSS 6.9), this v
A zip slip vulnerability in the component \service\migrate\MigrateForm.java of JEEWMS v3.7 allows attackers to execute a
Jeewms 3.7 contains a server-side request forgery vulnerability in the UEditor plugin's getRemoteImage.jsp file, where t
Code injection in erzhongxmu JeeWMS via the JimuReport test-connection endpoint (/base-boot/jmreport/testConnection) all
Unauthenticated remote access to the Spring Boot Actuator endpoint in erzhongxmu JeeWMS exposes sensitive application in
A vulnerability was found in erzhongxmu Jeewms up to 20241108. Rated medium severity (CVSS 5.3), this vulnerability is r
A vulnerability was found in Guangzhou Huayi Intelligent Technology Jeewms up to 1.0.0 and classified as critical.html o
JEEWMS 1.0 is vulnerable to SQL Injection. Attackers can inject malicious SQL statements through the id1 and id2 paramet
Reflected cross-site scripting in Jeewms up to version 3.7 exists in the UEditor component's getContent.jsp file through
Cross-site scripting (XSS) in the doAdd function of Jeewms up to version 3.7 allows unauthenticated remote attackers to
EUVD-2026-97136
GHSA-773r-fc25-xg9p
NVD
CVE.org
EPSS
VulDB
Exploit-DB