CVE-2025-5387
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 · uneditedA vulnerability classified as critical has been found in JeeWMS up to 20250504. Affected is the function dogenerate of the file /generateController.do?dogenerate of the component File Handler. The manipulation leads to improper access controls. It is possible to launch the attack remotely. This product is using a rolling release to provide continious delivery. Therefore, no version details for 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 confidenceJeeWMS contains a critical improper access control vulnerability in the file generation endpoint /generateController.do?dogenerate. The dogenerate function lacks proper authentication or authorization checks, allowing remote unauthenticated attackers to trigger file generation operations. With a CVSS 9.8, this is easily exploitable over the network and can lead to unauthorized file creation or exposure.
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<= 2025-05-04CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Jeewms installation and versionLocate the Jeewms application in your environment. Check version files, deployment metadata, or application banners for version information. Compare against the affected range (any version dated on or before 2025-05-04).Affected if The installed version is dated on or before May 4, 2025.
-
Confirm /generateController.do endpoint existsLocate the web application deployment directory and search for the file generateController.do, or use web scanning tools to probe for the presence of /generateController.do endpoint.Affected if The generateController.do file exists in the deployed application.
-
Test unauthenticated access to dogenerate functionSend an HTTP request to the endpoint (e.g., GET or POST to /generateController.do?dogenerate) without providing any authentication credentials or session cookies. Observe whether the application accepts the request.Affected if The endpoint responds without requiring authentication (returns 200 OK instead of redirecting to login or returning 401/403).
-
Check for authentication enforcement on file handler functionsReview application security configuration, Spring Security XML/annotations, or web.xml for URL access rules. Verify if /generateController.do or its dogenerate action is explicitly included in security filter chains or intercept-url patterns.Affected if No security constraint or access control rule is defined for the generateController.do endpoint.
You are affected if your Jeewms version is dated on or before 2025-05-04 and the /generateController.do endpoint is accessible without authentication.
Generated from the published advisory. Verify against your own configuration.
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 · scopedImplement proper authentication enforcement and role-based authorization checks on the dogenerate endpoint. Restrict file generation to authenticated, authorized users only, and validate all input parameters to prevent path traversal or arbitrary file creation.
Latest rolling release beyond 2025-05-04 (contact JeeWMS maintainers for exact version)
- 1. Immediately restrict network access to the /generateController.do endpoint using firewall rules or network segmentation
- 2. If the application has an admin dashboard, disable or restrict the generateController functionality until upgrade is complete
- 3. Contact JeeWMS official support or check gitee.com for the latest rolling release version that includes the security fix
- 4. Upgrade to the latest available version of JeeWMS beyond the 2025-05-04 release
- 5. After upgrade, verify that the /generateController.do?dogenerate endpoint requires proper authentication and authorization
- 6. Review user role assignments to ensure only privileged users can access file generation functions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5387 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-5387 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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