dbcve.org
JsherpApplication · Jishenghua

CVE-2026-1546

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-28
Fix available
A fix is available. Upgrade to after 3.6 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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 vulnerability has been detected in jishenghua jshERP up to 3.6. The impacted element is the function getBillItemByParam of the file /jshERP-boot/depotItem/importItemExcel of the component com.jsh.erp.datasource.mappers.DepotItemMapperEx. The manipulation of the argument barCodes leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.

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 jshERP up to v3.6 in the getBillItemByParam function within DepotItemMapperEx.java via the barCodes parameter of the /jshERP-boot/depotItem/importItemExcel endpoint, allowing remote attackers to execute arbitrary SQL queries.

MitigationReplace dynamic SQL construction with parameterized queries/prepared statements for the barCodes parameter in the DepotItemMapperEx mapper, and implement input validation on all user-supplied parameters before database operations.

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
JsherpApplication
Affected:<= 3.6

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify jshERP installation
    Search for jshERP application files or check running Java processes for jshERP-boot related packages. Look for the presence of jshERP-boot or Jsherp directories in the deployment path.
    Affected if jshERP or jshERP-boot application files are present on the system
  2. Determine installed jshERP version
    Locate the version file or build metadata. Common locations: version file in WEB-INF/classes, pom.xml version, or application properties version setting. Compare against affected version <= 3.6.
    Affected if The installed version is 3.6 or any earlier version
  3. Locate vulnerable mapper file
    Search for DepotItemMapperEx.java in the deployed application codebase, typically under src/main/java or in decompiled class files. Look for the getBillItemByParam function definition.
    Affected if The file DepotItemMapperEx.java with getBillItemByParam function exists in the deployment
  4. Check endpoint exposure
    Verify if the /jshERP-boot/depotItem/importItemExcel REST endpoint is accessible. This typically requires network access to the application's web services port.
    Affected if The importItemExcel endpoint is exposed and accepts requests

A defender is affected if jshERP version 3.6 or lower is deployed AND the DepotItemMapperEx.java with the vulnerable getBillItemByParam function exists AND the importItemExcel endpoint is accessible in their environment.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.6
Interim mitigation

Replace dynamic SQL construction with parameterized queries/prepared statements for the barCodes parameter in the DepotItemMapperEx mapper, and implement input validation on all user-supplied parameters before database operations.

Recommended fix High confidence
  1. No vendor patch or fixed release is currently available for this vulnerability.
  2. The project maintainers were notified but have not responded according to the official description.
  3. Monitor the official jshERP/Jsherp repository for future security releases.
  4. Consider implementing input validation and parameterized queries as a temporary workaround if possible.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jsherp Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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