Skip to main content
CVE-2025-51744VulnerabilityPublished Updated

CVE-2025-51744: JSH_ERP · n/a

Affects JSH_ERPSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% 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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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-26.

What to do

Affected software

ProductAffectedFixed in
GitHubjishenghua/JSH_ERPpkg:github/jishenghua/JSH_ERPOther threatsAffected
  • =2.3.1
Fixed in–

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

AI-suggested

1. Immediately restrict access to the /user/addUser endpoint by implementing network-level controls such as IP whitelisting or VPN requirements to limit exposure. 2. Employ Web Application Firewalls (WAFs) with custom rules to detect and block malicious deserialization payloads targeting fastjson vulnerabilities. 3. If possible, disable or remove the vulnerable endpoint until a vendor patch is available. 4. Implement strict input validation and sanitization on all JSON inputs to prevent malicious object injection. 5. Monitor logs for unusual activity or malformed JSON requests indicative of exploitation attempts. 6. Segment the ERP system network to minimize lateral movement if compromise occurs. 7. Engage with the vendor for timely patches or updates and apply them as soon as they are released. 8. Conduct internal security assessments and penetration tests focusing on deserialization vulnerabilities. 9. Educate development and security teams about the risks of unsafe deserialization and secure coding practices. 10. Prepare incident response plans specific to ERP system compromises to reduce response time in case of exploitation.

Description

An issue was discovered in jishenghua JSH_ERP 2.3.1. The /user/addUser endpoint is vulnerable to fastjson deserialization attacks.

References

Community reviews

Loading reviews…