CVE-2025-5390
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, which was classified as critical, was found in JeeWMS up to 20250504. This affects the function filedeal of the file /systemController/filedeal.do of the component File Handler. The manipulation leads to improper access controls. It is possible to initiate the attack remotely. This product does not use versioning. This is why information about affected and unaffected releases are unavailable.
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 confidenceA critical improper access control vulnerability exists in JeeWMS in the filedeal function at /systemController/filedeal.do. The file handler component lacks proper authentication or authorization checks, allowing remote unauthenticated attackers to manipulate file operations. Given the CVSS 9.8 and remote exploitability, this likely enables unauthorized file upload, read, write, or deletion.
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.
-
Confirm JeeWMS is installedIdentify if the JeeWMS application is running in your environment by checking for Java processes hosting the application or by accessing the web interface on common ports (8080, 8090, etc.)Affected if JeeWMS is present in the environment
-
Determine installed versionLocate the version information in the application by checking the WAR file, version manifest, or logging into the admin interface and navigating to the system or about pageAffected if The installed version is at or before the 2025-05-04 release
-
Verify endpoint accessibilitySend an HTTP request to /systemController/filedeal.do without providing any authentication credentials or session cookiesAffected if The endpoint responds without requiring login or authentication
-
Test file operation behaviorAttempt a GET request to the filedeal endpoint with common file operation parameters (such as read, write, or delete operations) using a tool like curl or Burp Suite, without authenticationAffected if The server processes the request and returns file operation results without rejecting it
-
Review authentication configurationInspect the application configuration files (such as Spring security XML or annotation-based security settings) to verify whether the /systemController/filedeal.do path is explicitly excluded from authentication requirementsAffected if The endpoint lacks authentication constraints in the security configuration
A user is affected if JeeWMS (Huayi Tec Jeewms) version 2025-05-04 or earlier is running and the /systemController/filedeal.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.
From vendor dataImplement proper authentication and role-based authorization checks on the filedeal endpoint, validate all file operations, and restrict file type uploads. Consider disabling the endpoint until a patch is available.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5390 — 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-5390 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