CVE-2026-1546VulnerabilityPublished 28 Jan 2026Updated 23 Feb 2026

CVE-2026-1546: jishenghua jshERP · SQL Injection

Affects jishenghua jshERPSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
jishenghuajshERP	Affected =3.0 =3.1 =3.2 =3.3 =3.4 =3.5 =3.6	Fixed in–
GitHubjishenghua/jshERP`pkg:github/jishenghua/jshERP`Other threats	Affected =3.0 =3.1 =3.2 =3.3 =3.4 =3.5 =3.6	Fixed in–

CPE configurations (1)

cpe:2.3:a:jishenghua:jsherp:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-1546, organizations should first assess their exposure by identifying all instances of jshERP versions 3.0 through 3.6 in their environment. Immediate steps include restricting network access to the ERP system, especially from untrusted or public networks, by implementing firewall rules or VPN requirements. Employ web application firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the barCodes parameter. Conduct thorough input validation and sanitization on all user-supplied data at the application level, if source code access and modification are possible. Monitor logs for unusual database query patterns or errors indicative of injection attempts. Engage in active threat hunting to detect potential exploitation. Coordinate with the vendor for updates or patches and apply them promptly once available. Consider isolating the ERP system within a segmented network zone to limit lateral movement in case of compromise. Finally, educate relevant personnel about the vulnerability and ensure incident response plans include scenarios involving ERP system breaches.

Description

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.

Impact

The SQL injection vulnerability in jshERP can have significant impacts on organizations using the affected versions. Attackers exploiting this flaw can gain unauthorized access to sensitive business data, including financial records, inventory details, and customer information. They may also alter or delete critical data, leading to operational disruptions, financial losses, and reputational damage. Since jshERP is an enterprise resource planning system, the integrity and availability of its data are crucial for daily business functions. Exploitation could facilitate further attacks, such as privilege escalation or lateral movement within the network. The remote and unauthenticated nature of the vulnerability increases the likelihood of exploitation, especially in environments where the ERP system is exposed to untrusted networks. Organizations lacking timely detection and response capabilities may face prolonged exposure and increased damage. Additionally, the absence of an official patch means that mitigation relies on workarounds or compensating controls, which may not fully eliminate risk.

Summary

CVE-2026-1546 identifies a SQL injection vulnerability in the jishenghua jshERP software, versions 3.0 through 3.6. The vulnerability resides in the getBillItemByParam function located in the /jshERP-boot/depotItem/importItemExcel file, within the com.jsh.erp.datasource.mappers.DepotItemMapperEx component. The issue arises from improper sanitization or validation of the barCodes parameter, which is directly used in SQL queries, enabling attackers to inject arbitrary SQL commands. This injection can be performed remotely without authentication or user interaction, increasing the attack surface. The CVSS 4.0 score of 5.3 reflects a medium severity, considering the ease of remote exploitation and the potential for partial confidentiality, integrity, and availability impacts. Exploitation could allow attackers to read, modify, or delete sensitive data within the ERP database, potentially disrupting business operations or exposing confidential information. The lack of authentication requirement and the public availability of exploit details heighten the risk. The vulnerability affects all listed versions from 3.0 to 3.6, indicating a long-standing issue in the product's codebase.

References

Community reviews

Loading reviews…