dbcve.org
JeewmsApplication · Huayi Tec

CVE-2025-5388

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-31
Fix available
A fix is available. Upgrade to after 2025-05-04 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in JeeWMS allows remote attackers to execute arbitrary SQL commands via the dogenerate function in /generateController.do. The vulnerability takes advantage of unsanitized input being passed directly to database queries in the affected endpoint.

MitigationImmediately restrict network access to the affected endpoint pending a fix. Implement parameterized queries or prepared statements to sanitize user input before executing SQL statements. Consider deploying a WAF rule as a temporary compensating control.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JeewmsApplication
Affected:<= 2025-05-04

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm JeeWMS installation
    Identify if Huayi Tec Jeewms is deployed in your environment by checking for the application codebase, web archives, or running services on typical ports (common web server ports 80, 443, 8080). Look for Jeewms or JeeWMS references in installed software listings or documentation.
    Affected if The application is not present or has been removed entirely.
  2. Verify product version
    Locate the installed version of Huayi Tec Jeewms by checking the application manifest, build files, version metadata files, or the about/admin panel if available. Compare the version or build date against the affected range: versions dated 2025-05-04 or earlier.
    Affected if The installed version is dated 2025-05-04 or earlier, or the version number falls within the affected release timeline.
  3. Check endpoint exposure
    Attempt to access the vulnerable endpoint by making an HTTP request to /generateController.do (or locating it in the deployed web application files). Determine if this endpoint is exposed and reachable from your network.
    Affected if The /generateController.do endpoint exists and is network-accessible.
  4. Identify dogenerate function
    Inspect the generateController.do source code or decompiled classes to locate the dogenerate function. Verify whether it handles user-supplied input and passes it directly to database queries without sanitization or parameterized queries.
    Affected if The dogenerate function is present and processes unsanitized input in SQL queries.
  5. Review access logs
    Examine web server and application access logs for requests to /generateController.do with parameters that may indicate SQL injection testing or exploitation attempts. Look for unusual SQL syntax in query parameters.
    Affected if Suspicious SQL injection patterns are found in logs targeting the dogenerate function.

Your environment is affected if Huayi Tec Jeewms version 2025-05-04 or earlier is installed, the /generateController.do endpoint is accessible, and the dogenerate function processes unsanitized input into SQL queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2025-05-04
Interim mitigation

Immediately restrict network access to the affected endpoint pending a fix. Implement parameterized queries or prepared statements to sanitize user input before executing SQL statements. Consider deploying a WAF rule as a temporary compensating control.

Recommended fix Moderate confidence
  1. Restrict network access to the JeeWMS application to minimize remote attack surface
  2. Contact JeeWMS vendor to request the latest rolling release patch that addresses CVE-2025-5388
  3. Apply the vendor-provided patch/updated rolling release to address the SQL injection in /generateController.do?dogenerate
  4. After patching, verify the fix by testing the dogenerate endpoint with both valid and invalid input to confirm SQL injection is mitigated
  5. Monitor application logs for any suspicious SQL injection attempts targeting the generateController endpoint

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jeewms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,580
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5388 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-5388 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data