Security readout for executives and security teams
Plain-English summary
CVE-2026-1546 is a SQL injection issue in jishenghua jshERP through version 3.6. A remote, logged-in user may be able to manipulate database queries through the item import workflow. Public exploit details are reported, but the sources do not show confirmed active exploitation or an official vendor fix.
Executive priority
Treat as a near-term remediation item for any production jshERP deployment. Prioritize systems exposed beyond trusted internal users or used by many authenticated staff. The issue is not confirmed as actively exploited, but public exploit disclosure raises urgency.
Technical view
The reported flaw affects getBillItemByParam in com.jsh.erp.datasource.mappers.DepotItemMapperEx, reached through /jshERP-boot/depotItem/importItemExcel. The barCodes argument can lead to SQL injection. CVSS v2 is 6.5 with network access, low complexity, single authentication, and partial confidentiality, integrity, and availability impact.
Likely exposure
Organizations running jishenghua jshERP versions 3.0 through 3.6 are potentially exposed, especially where authenticated users can access depot item Excel import functionality. Internet exposure increases operational risk, but the CVSS data indicates authentication is required.
Exploitation context
VulDB states that an exploit has been publicly disclosed and may be used. The CVE is not listed as KEV in the provided bundle, and no cited source confirms active exploitation in the wild.
Researcher notes
Evidence comes from the CVE record, VulDB, and a GitHub issue. The report says the project was notified but had not responded. Do not assume a patch exists from these sources. Validate exposure defensively without using public exploit material.
Mitigation direction
- Check the jshERP project and vendor channels for an official fix or guidance.
- Restrict access to jshERP import functions to trusted, necessary users only.
- Reduce external exposure of jshERP administrative or import interfaces.
- Review database privileges used by the application for least privilege.
- Monitor application and database logs for unusual import or query activity.
Validation and detection
- Inventory jshERP deployments and confirm versions in use.
- Identify whether versions 3.0 through 3.6 are present.
- Confirm who can access /jshERP-boot/depotItem/importItemExcel functionality.
- Review logs for suspicious use of the barCodes parameter.
- Track GitHub issue 145 and VulDB for vendor response or updates.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-1546 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR86.4Primary CVE scoreVulnerability scoring details
Base CVSS 2.0 score
6.5MediumVector: AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
Source materials
- CVE List V5 sourceCVE List V5
- VDB-343230 | jishenghua jshERP com.jsh.erp.datasource.mappers.DepotItemMapperEx importItemExcel getBillItemByParam sql injectionCVE reference · vdb-entry, technical-description
- VDB-343230 | CTI Indicators (IOB, IOC, TTP, IOA)CVE reference · signature, permissions-required
- Submit #739688 | https://github.com/jishenghua/jshERP jshERP v3.6 SQL InjectionCVE reference · third-party-advisory
- https://github.com/jishenghua/jshERP/issues/145CVE reference · issue-tracking, exploit
- https://github.com/jishenghua/jshERP/CVE reference · product
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.