Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-108782 Overview
CVE-2026-108782 is a SQL injection vulnerability in erzhongxmu JEEWMS up to version 2026.09.27-W39. The flaw resides in the CommonServiceImpl.getAutoList function within src/main/java/org/jeecgframework/core/common/service/impl/CommonServiceImpl.java, part of the Autocomplete Handler component. Attackers can manipulate the trem, searchField, or entityName arguments to inject arbitrary SQL. The attack is remotely exploitable and requires only low-level authentication. Public exploit code is available. The vendor did not respond to disclosure attempts, leaving affected installations without an official patch.
Critical Impact
Authenticated remote attackers can inject SQL statements through the Autocomplete Handler, potentially reading, modifying, or deleting database contents.
Affected Products
- erzhongxmu JEEWMS versions up to and including 2026.09.27-W39
- Component: Autocomplete Handler (CommonServiceImpl.getAutoList)
- Source file: src/main/java/org/jeecgframework/core/common/service/impl/CommonServiceImpl.java
Discovery Timeline
- 2026-10-12 - CVE-2026-108782 published to NVD
- 2026-10-15 - Last updated in NVD database
Technical Details for CVE-2026-108782
Vulnerability Analysis
The vulnerability is classified under CWE-74, improper neutralization of special elements in output used by a downstream component (injection). The getAutoList method accepts user-controlled parameters that are concatenated into SQL queries without parameterization or sanitization.
An authenticated attacker who can reach the autocomplete endpoint can craft requests that modify the query logic. Successful exploitation grants read and write access to the underlying database within the privileges of the application's database user.
Public exploit code has been released, lowering the barrier to opportunistic attacks against exposed JEEWMS deployments.
Root Cause
The getAutoList method constructs dynamic SQL by appending the trem (search term), searchField (column name), and entityName (table or entity reference) parameters directly into the query string. Because searchField and entityName reference schema objects, they cannot be bound as prepared-statement parameters, and the code performs no allowlist validation before interpolating them into SQL.
Attack Vector
Exploitation requires network access to the JEEWMS web interface and valid low-privilege credentials. The attacker submits a request to the autocomplete handler with injected SQL payloads in the trem, searchField, or entityName parameters. The server executes the manipulated query against the backend database. For technical references, see VulDB entry 416561 and the VulDB CVE record.
Detection Methods for CVE-2026-108782
Indicators of Compromise
- Web server access logs containing autocomplete endpoint requests with SQL meta-characters (', --, UNION, SLEEP() in the trem, searchField, or entityName parameters
- Database audit logs showing unexpected UNION SELECT, INFORMATION_SCHEMA queries, or queries against entities not referenced by normal application workflows
- Application error entries referencing CommonServiceImpl.getAutoList with SQL syntax exceptions
Detection Strategies
- Deploy database activity monitoring to flag malformed queries originating from the JEEWMS application account
- Create web application firewall rules that inspect autocomplete request parameters for SQL injection signatures
- Review authentication logs for low-privilege accounts issuing abnormal volumes of autocomplete requests
Monitoring Recommendations
- Alert on HTTP responses with elevated latency or large payloads from the autocomplete endpoint, which can indicate time-based or UNION-based extraction
- Correlate failed login attempts with subsequent authenticated autocomplete traffic to catch credential-stuffing precursors
- Baseline the normal entityName and searchField values the application uses and alert on deviations
How to Mitigate CVE-2026-108782
Immediate Actions Required
- Restrict network exposure of JEEWMS management interfaces to trusted networks or VPN only
- Rotate credentials for all low-privilege application accounts that could reach the autocomplete endpoint
- Reduce the database user's privileges to the minimum required by the application, removing DDL and administrative rights
Patch Information
No vendor patch is available. The upstream project maintainer did not respond to the disclosure. Organizations should track the VulDB vulnerability record for future updates and consider migrating off the affected release or applying compensating controls described below.
Workarounds
- Place a web application firewall in front of JEEWMS with strict allowlists for the searchField and entityName parameters
- Disable or block the autocomplete handler route at the reverse proxy if the feature is not required
- If source modification is feasible, patch CommonServiceImpl.getAutoList to validate searchField and entityName against an allowlist of permitted schema identifiers and bind trem as a parameterized query value
# Example reverse proxy rule to block autocomplete requests with suspicious characters
location ~* /.*autoList.* {
if ($args ~* "(union|select|sleep\(|--|')") {
return 403;
}
proxy_pass http://jeewms_backend;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

