CVE-2025-5384
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 was found in JeeWMS up to 20250504. It has been classified as critical. This affects the function CgAutoListController of the file /cgAutoListController.do?datagrid. The manipulation leads to sql injection. It is possible to initiate the attack 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 confidenceA SQL injection vulnerability exists in JeeWMS in the CgAutoListController function at the /cgAutoListController.do?datagrid endpoint. Attackers can manipulate the datagrid parameter to inject malicious SQL queries. The vulnerability is remotely exploitable and carries a critical CVSS score of 9.8.
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 installationIdentify if the target application is JeeWMS by examining deployed web application artifacts. Look for JeeWMS-specific files, directory structures, or application identifiers in the web root, WAR file contents, or application metadata.Affected if The application is confirmed to be JeeWMS
-
Determine JeeWMS versionLocate version information within the JeeWMS deployment. Check version files, build manifests, about pages, or configuration descriptors that ship with the application. Compare the found version against the affected range of versions <= 2025-05-04.Affected if The installed version is 2025-05-04 or earlier
-
Verify endpoint accessibilityConfirm that the /cgAutoListController.do endpoint is exposed on the web server. Test for endpoint availability via HTTP request or review web server access logs for requests to this path.Affected if The /cgAutoListController.do endpoint is reachable over the network
-
Check datagrid parameter exposureDetermine whether the datagrid parameter can be supplied to the CgAutoListController endpoint. This parameter is the injection vector for this vulnerability.Affected if User-supplied input to the datagrid parameter is accepted without validation
The environment is affected if it runs Huayi Tec Jeewms version 2025-05-04 or earlier with the /cgAutoListController.do endpoint accessible and the datagrid parameter exposed to user input.
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 input validation and parameterized queries (prepared statements) in the CgAutoListController function to neutralize SQL injection vectors. Apply a WAF as an interim protective measure while the code fix is developed and deployed.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5384 — 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-5384 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