CVE-2025-5384VulnerabilityPublished 31 May 2025Updated 2 Jun 2025

CVE-2025-5384: JeeWMS · SQL Injection

Affects JeeWMSSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 31 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHuberzhongxmu/JEEWMS`pkg:github/erzhongxmu/JEEWMS`Other threats	Affected–	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should implement the following specific mitigations: 1) Conduct an immediate audit to identify all instances of JeeWMS in use and verify the version to assess exposure. 2) Restrict network access to the JeeWMS management interface, limiting it to trusted internal IP addresses or VPN connections to reduce exposure to remote attacks. 3) Employ web application firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the /cgAutoListController.do?datagrid endpoint. 4) Monitor application logs for unusual query parameters or error messages indicative of injection attempts. 5) Engage with the JeeWMS vendor or community to obtain or request patches or updates addressing this vulnerability. 6) If possible, implement input validation and parameterized queries at the application layer to prevent injection. 7) Prepare incident response plans specific to database compromise scenarios, including data integrity verification and recovery procedures. 8) Consider isolating the JeeWMS environment in segmented network zones to contain potential breaches.

Description

A vulnerability was found in JeeWMS up to 20250504. It has been classified as critical. This affects the function CgAutoListController of the file /cgAutoListController.do?datagrid. The manipulation leads to sql injection. It is possible to initiate the attack remotely. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available.

Impact

For European organizations using JeeWMS, this vulnerability poses a risk of unauthorized database access or manipulation, potentially leading to data leakage, corruption, or disruption of warehouse management operations. Given the medium severity and low impact ratings, the immediate risk may be limited; however, attackers could leverage this vulnerability as part of a multi-stage attack to escalate privileges or move laterally within a network. The potential impact includes exposure of sensitive business data, disruption of supply chain logistics, and operational downtime. Organizations in sectors relying heavily on inventory and warehouse management, such as manufacturing, retail, and logistics, could face operational challenges. Additionally, regulatory compliance risks may arise if personal or sensitive data is exposed due to the vulnerability, implicating GDPR obligations. The lack of available patches and the rolling release model complicate timely remediation, increasing the window of exposure.

Summary

CVE-2025-5384 is a SQL Injection vulnerability identified in JeeWMS, specifically affecting the function CgAutoListController within the /cgAutoListController.do?datagrid endpoint. This vulnerability allows an unauthenticated remote attacker with low privileges to manipulate input parameters to inject malicious SQL commands, potentially compromising the underlying database. The vulnerability exists in versions up to 20250504, but due to JeeWMS's rolling release model, exact version details for affected and patched releases are not clearly delineated. The CVSS 4.0 base score is 5.3, indicating a medium severity level. The vector indicates network attack vector (AV:N), low attack complexity (AC:L), no authentication required (AT:N), no user interaction (UI:N), and low impact on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). Although the impact on CIA triad components is low, the ability to remotely inject SQL commands can lead to unauthorized data access or modification if chained with other vulnerabilities or misconfigurations. No known exploits are currently reported in the wild, and no patches or vendor advisories have been linked yet. The vulnerability's presence in a web-based management system like JeeWMS, which is likely used for warehouse or inventory management, raises concerns about data integrity and operational continuity if exploited.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Jul 2025, 00:55 UTC

Technical details

References

Community reviews

Related threats