dbcve.org
JeewmsApplication · Huayi Tec

CVE-2025-5389

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, which was classified as critical, has been found in JeeWMS up to 20250504. Affected by this issue is the function dogenerateOne2Many of the file /generateController.do?dogenerateOne2Many of the component File Handler. The manipulation leads to improper access controls. The attack may be launched remotely. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are 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 · moderate confidence

A critical improper access control vulnerability exists in JeeWMS within the file handler component's dogenerateOne2Many function accessible via /generateController.do. The endpoint lacks proper authentication and authorization checks, allowing unauthenticated remote attackers to potentially generate, read, or manipulate files on the server. Given the CVSS 9.8 rating, this is easily exploitable over the network with no user interaction required.

MitigationImplement robust authentication and role-based authorization checks on all file handler endpoints, particularly the generateController functions. Restrict the dogenerateOne2Many functionality to authenticated, authorized administrative users only, and disable or remove the endpoint if not required for production.

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. Identify Jeewms installation
    Check your web application for the presence of JeewMS from Huayi Tec. Look for application fingerprints, banner information, or check the software inventory for 'JeewMS' or 'Huayi Tec' in the deployed applications.
    Affected if The application is Huayi Tec Jeewms and the version is <= 2025-05-04
  2. Locate generateController.do endpoint
    Check your web server configuration or run a web path scan for /generateController.do. This endpoint should exist in the deployed JeewMS application directory.
    Affected if The endpoint /generateController.do is accessible and responding on your server
  3. Verify unauthenticated access to dogenerateOne2Many
    Send an HTTP request to /generateController.do with the action parameter for dogenerateOne2Many (e.g., ?action=dogenerateOne2Many or similar parameter used by the function) without providing any authentication credentials or session cookies. Inspect the HTTP response to see if the function executes without returning an authentication error.
    Affected if The request completes without requiring authentication and returns a successful response indicating the function executed
  4. Check file generation capability exposure
    Review the HTTP response from the unauthenticated request to determine if file generation, reading, or manipulation occurred. Look for indicators such as file paths in responses, generated files in the deployment directory, or success messages related to file operations.
    Affected if The dogenerateOne2Many function executes and allows file operations without authentication
  5. Confirm version against affected range
    Determine the installed JeewMS version by checking the application build files, version manifest, or framework metadata. Compare this version to the affected range: <= 2025-05-04.
    Affected if Your installed JeewMS version is 2025-05-04 or earlier

You are affected if your environment runs Huayi Tec Jeewms version 2025-05-04 or earlier, and the /generateController.do endpoint with the dogenerateOne2Many function is exposed and accessible without authentication.

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.

From vendor data
Upgrade available Upgrade to a release after 2025-05-04
Interim mitigation

Implement robust authentication and role-based authorization checks on all file handler endpoints, particularly the generateController functions. Restrict the dogenerateOne2Many functionality to authenticated, authorized administrative users only, and disable or remove the endpoint if not required for production.

Fix this in Jeewms Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA6.0 h
50.0 hours of engineering $8,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5389 — 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-5389 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