dbcve.org
JeewmsApplication · Huayi Tec

CVE-2025-5385

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 was found in JeeWMS up to 20250504. It has been declared as critical. This vulnerability affects the function doAdd of the file /cgformTemplateController.do?doAdd. The manipulation leads to path traversal. The attack can be initiated 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 path traversal vulnerability exists in JeeWMS in the doAdd function of /cgformTemplateController.do. The vulnerability allows remote attackers to manipulate file paths using directory traversal sequences (e.g., ../../) to access sensitive files outside the intended web root directory. This could enable unauthorized file access or potentially remote code execution depending on file write capabilities.

MitigationImplement strict input validation and sanitization on file path parameters in the doAdd function, using allowlist validation and canonicalizing paths to prevent traversal sequences. Restrict file access permissions and ensure uploaded files are stored outside web-accessible directories.

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 from Huayi Tec
    Identify if the application is Huayi Tec Jeewms by checking the application banner, login page, or administrative interface for Jeewms branding. Look for version information in the admin panel or system information page.
    Affected if The application is confirmed to be Huayi Tec Jeewms
  2. Determine installed version
    Locate the version information for the Jeewms installation. Check the admin control panel, system configuration files, or the application footer for a build date or version number. Compare against the affected range of <= 2025-05-04.
    Affected if The installed version is dated 2025-05-04 or earlier, or the version number indicates an unpatched release
  3. Verify vulnerable endpoint exists
    Check if the endpoint /cgformTemplateController.do is accessible in the web application. This can be done by attempting to access the URL or reviewing the deployed web application files for the presence of the cgformTemplateController class.
    Affected if The /cgformTemplateController.do endpoint is present and accessible
  4. Check if doAdd function handles file paths
    Examine the cgformTemplateController implementation to determine if the doAdd function accepts and processes file path parameters. This may require source code review or testing the endpoint with path traversal inputs in a controlled environment.
    Affected if The doAdd function accepts file path parameters without proper validation

A user is affected if they are running Huayi Tec Jeewms version dated 2025-05-04 or earlier with the /cgformTemplateController.do endpoint accessible and the doAdd function handling user-supplied file paths.

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 strict input validation and sanitization on file path parameters in the doAdd function, using allowlist validation and canonicalizing paths to prevent traversal sequences. Restrict file access permissions and ensure uploaded files are stored outside web-accessible directories.

Fix this in Jeewms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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