VulnerabilityPublished 6 Feb 2024Updated 26 Aug 2024

CVE-2024-24002: jshERP · SQL Injection

Source CVE Database V5

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score

9.8Critical

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Feb 2024
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 26 Oct 2026.

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 or the CVSS exploit maturity 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

AI-suggested

To mitigate CVE-2024-24002, organizations should immediately implement the following measures: 1) Apply any available patches or updates from the jshERP vendor once released. 2) If patches are unavailable, restrict access to the vulnerable MaterialController endpoints via network segmentation or firewall rules to limit exposure. 3) Implement strict input validation and sanitization on the 'column' and 'order' parameters at the application level, employing whitelisting of acceptable values rather than blacklisting. 4) Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting these parameters. 5) Conduct thorough code reviews and security testing of ERP modules to identify and remediate similar injection flaws. 6) Monitor database logs and application logs for anomalous queries or error messages indicative of injection attempts. 7) Educate development teams on secure coding practices, particularly regarding dynamic SQL query construction. These targeted actions go beyond generic advice and address the root cause and attack vector of this specific vulnerability.

Description

jshERP v3.3 is vulnerable to SQL Injection. The com.jsh.erp.controller.MaterialController: com.jsh.erp.utils.BaseResponseInfo getListWithStock() function of jshERP does not filter `column` and `order` parameters well enough, and an attacker can construct malicious payload to bypass jshERP's protection mechanism in `safeSqlParse` method for sql injection.

Impact

The impact of CVE-2024-24002 is severe, as successful exploitation allows attackers to execute arbitrary SQL commands on the backend database without authentication. This can lead to unauthorized disclosure of sensitive business data, modification or deletion of critical records, and potentially full system compromise if the database server is leveraged to execute further commands. The integrity of business operations relying on jshERP could be severely disrupted, causing financial loss, reputational damage, and regulatory compliance violations. Availability may also be affected if attackers delete or corrupt essential data. Given the network-exploitable nature and lack of required privileges, the vulnerability poses a significant threat to any organization using the affected software version, especially those handling sensitive inventory, financial, or operational data.

Summary

CVE-2024-24002 identifies a critical SQL Injection vulnerability in the jshERP version 3.3 software, specifically within the MaterialController's getListWithStock() function. This function accepts 'column' and 'order' parameters that are intended to control SQL query sorting but are insufficiently sanitized. The vulnerability stems from a flawed implementation of the safeSqlParse method, which fails to adequately filter or validate these parameters, allowing attackers to inject malicious SQL payloads. Such injection can manipulate backend database queries, potentially enabling unauthorized data access, data modification, or deletion. The vulnerability requires no privileges or user interaction, making it trivially exploitable remotely over the network. The CVSS v3.1 score of 9.8 reflects the high impact on confidentiality, integrity, and availability, with an attack vector of network and low attack complexity. No patches or official fixes are currently listed, and no public exploits are known yet, but the risk remains critical due to the nature of SQL Injection attacks. This vulnerability is categorized under CWE-89, a common and dangerous injection flaw. Organizations using jshERP for enterprise resource planning should urgently assess exposure and implement mitigations to prevent exploitation.

CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #2OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Parameterization
If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
OWASP Cheat Sheets
Query Parameterization (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.4 (opens in a new tab)
V5.3.5 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Command Line Execution through SQL Injection (opens in a new tab)
Object Relational Mapping Injection (opens in a new tab)
SQL Injection through SOAP Parameter Tampering (opens in a new tab)
Expanding Control over the Operating System from the Database (opens in a new tab)
SQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 26 Feb 2026, 10:18 UTC

WeaknessesCWE-89

Technical details

References

Community reviews

Related threats