VulnerabilityPublished 31 May 2025Updated 2 Jun 2025

CVE-2025-5388: JeeWMS · SQL Injection

Affects JeeWMSSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 11:42 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 29% 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 26 Oct 2026.

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 or the CVSS exploit maturity 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

Immediate review and restriction of access controls to the /generateController.do?dogenerate endpoint to limit exposure only to trusted users and systems.
Implement input validation and parameterized queries or prepared statements in the dogenerate function to prevent SQL injection.
Monitor database logs and application logs for unusual queries or access patterns indicative of injection attempts.
Conduct a thorough security audit of the entire JeeWMS codebase to identify and remediate other potential injection points.
If possible, deploy Web Application Firewalls (WAF) with custom rules to detect and block SQL injection payloads targeting JeeWMS endpoints.
Coordinate with JeeWMS vendors or community to obtain patches or updates as they become available, given the rolling release model.
Regularly back up databases and test restoration procedures to minimize impact in case of data corruption or deletion.
Educate system administrators and developers on secure coding practices and the risks of SQL injection to prevent future vulnerabilities.

Description

A vulnerability classified as critical was found in JeeWMS up to 20250504. Affected by this vulnerability is the function dogenerate of the file /generateController.do?dogenerate. The manipulation leads to sql injection. The attack can be launched 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 could lead to unauthorized data access, data corruption, or denial of service within their warehouse management systems. Since JeeWMS likely manages inventory, logistics, and supply chain data, exploitation could disrupt critical business operations, cause financial losses, and damage trust with partners and customers. The ability to remotely exploit the vulnerability without user interaction increases the risk of automated attacks or exploitation by remote adversaries. Data breaches resulting from this vulnerability could also trigger regulatory consequences under GDPR, including fines and mandatory breach notifications. Organizations relying on JeeWMS for operational continuity may face downtime or degraded service quality if attackers manipulate or delete critical database records. The medium CVSS score reflects limited impact scope but does not diminish the importance of timely remediation, especially in sectors where supply chain integrity is crucial.

Summary

CVE-2025-5388 is a SQL Injection vulnerability identified in JeeWMS, a web-based warehouse management system. The vulnerability exists in the 'dogenerate' function accessed via the /generateController.do?dogenerate endpoint. This flaw allows an attacker to manipulate input parameters to inject malicious SQL commands, potentially compromising the backend database. The vulnerability is remotely exploitable without user interaction and requires low attack complexity, but does require some level of privileges (PR:L) indicating that the attacker must have limited privileges on the system to exploit it. The CVSS 4.0 vector indicates no user interaction (UI:N), no privileges required (PR:L), and low complexity (AC:L), with limited impact on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). JeeWMS uses a rolling release model, which complicates precise version tracking, but the affected version is identified as 20250504 or earlier. No patches or known exploits in the wild have been reported yet. The vulnerability could allow attackers to extract sensitive data, modify or delete records, or disrupt database operations, depending on the database permissions and the extent of injection possible. Given the nature of SQL Injection, this vulnerability poses a significant risk to data confidentiality and integrity within affected JeeWMS deployments.

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