dbcve.org
InjectionWeakness · CWE-74

CVE-2026-11457

HIGH · 7.3 CVSS v3.1 Published 2026-06-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 security flaw has been discovered in erzhongxmu JeeWMS up to 141740afb2ba14d441c82a833d0a418d07ca2d69. This vulnerability affects unknown code of the file /base-boot/jmreport/testConnection of the component JimuReport test-connection Endpoint. Performing a manipulation of the argument dbType/dbDriver/dbUrl/dbUsername/dbPassword results in injection. Remote exploitation of the attack is possible. The exploit has been released to the public and may be used for attacks. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.

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 confidence

SQL injection vulnerability in the JimuReport test-connection endpoint (/base-boot/jmreport/testConnection) of erzhongxmu JeeWMS. The endpoint accepts unsanitized input for database connection parameters (dbType, dbDriver, dbUrl, dbUsername, dbPassword), allowing remote attackers to inject malicious SQL commands. Public exploits are available.

MitigationImplement proper input validation and parameterized queries for database connection parameters. Consider restricting access to this endpoint or adding authentication. Alternatively, deploy a WAF rule to block injection attempts until the code fix is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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
    Identify if JeeWMS is deployed in your environment by checking for the presence of the application or its typical deployment artifacts (war files, JAR files, or web application directories containing 'jeewms' or 'JeeWMS' in the name).
    Affected if JeeWMS is installed and running in the environment.
  2. Locate the vulnerable endpoint
    Check if the URL path /base-boot/jmreport/testConnection is accessible by inspecting your web server's configured routes or by attempting a HEAD request to the endpoint (ensure this is done in an authorized testing environment only).
    Affected if The endpoint /base-boot/jmreport/testConnection responds to requests (returns any HTTP status other than 404).
  3. Verify endpoint accepts database connection parameters
    Inspect the application's API documentation, Swagger/OpenAPI definitions, or perform authorized traffic analysis to confirm the endpoint accepts the parameters: dbType, dbDriver, dbUrl, dbUsername, dbPassword.
    Affected if The endpoint accepts one or more of these database connection parameters (dbType, dbDriver, dbUrl, dbUsername, dbPassword).
  4. Check for input validation on connection parameters
    Review the application's source code (if accessible) or proxy logs to determine whether the endpoint implements input validation, sanitization, or parameterized queries for the database connection parameters before using them in SQL or connection operations.
    Affected if No input validation, sanitization, or parameterized queries are implemented for the database connection parameters, or validation is confirmed to be absent or weak.
  5. Assess network exposure of the endpoint
    Review firewall rules, web server access controls, or API gateway policies to determine if the /base-boot/jmreport/testConnection endpoint is accessible from untrusted networks or without authentication.
    Affected if The endpoint is exposed to untrusted networks or accessible without requiring administrator-level authentication.

If JeeWMS is installed, the testConnection endpoint is accessible, and no input validation is enforced on the database connection parameters (dbType, dbDriver, dbUrl, dbUsername, dbPassword), then the environment is affected by CVE-2026-11457.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and parameterized queries for database connection parameters. Consider restricting access to this endpoint or adding authentication. Alternatively, deploy a WAF rule to block injection attempts until the code fix is applied.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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