CVE-2025-70311
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 · uneditedJEEWMS 1.0 is vulnerable to SQL Injection. Attackers can inject malicious SQL statements through the id1 and id2 parameters in the /systemControl.do interface for attack.
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 confidenceJEEWMS 1.0 warehouse management system contains a SQL Injection vulnerability in the /systemControl.do endpoint. Attackers can inject malicious SQL commands through the id1 and id2 parameters, potentially allowing unauthorized database access, data exfiltration, or data manipulation.
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 dataall versionsCVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
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 installationLocate the Jeewms web application directory or check for 'jeewms' or 'JEEWMS' in deployed web applications. Look for the characteristic folder structure containing /systemControl.do or similar .do endpoints.Affected if Jeewms warehouse management system is deployed in the environment
-
Identify the vulnerable endpointCheck if the endpoint /systemControl.do exists in the deployed application. This endpoint is typically found under the /system/ or root control path.Affected if The systemControl.do endpoint is present and accessible in the web application
-
Verify vulnerable parameter acceptanceCheck if the id1 and id2 parameters are accepted by the systemControl.do endpoint. Review application logs or network traffic to confirm these parameters are processed by the endpoint.Affected if The id1 and id2 parameters are accepted and processed by the systemControl.do endpoint
-
Inspect SQL query implementationLocate the source code or decompile the application to examine the systemControl.do handler. Inspect the code that processes id1 and id2 parameters to determine if dynamic SQL concatenation is used without parameterized queries or input validation.Affected if The code handling id1/id2 parameters uses direct string concatenation to build SQL queries rather than prepared statements
The environment is affected if Jeewms is deployed with the systemControl.do endpoint present and accessible, as all versions of Huayi Tec Jeewms contain the SQL injection vulnerability in the id1 and id2 parameters.
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 dataReplace dynamic SQL queries with parameterized queries/prepared statements for the id1 and id2 parameters in the systemControl.do endpoint, and implement strict input validation to prevent SQL injection attacks.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-70311 — 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-70311 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