Skip to main content
VulnerabilityPublished Updated

CVE-2025-51746: JSH_ERP · Deserialization of Untrusted Data

Affects JSH_ERPSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 17:16 UTC

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

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. Immediate mitigation should focus on restricting access to the /serialNumber/addSerialNumber endpoint by implementing network-level controls such as IP whitelisting or VPN-only access.
  2. Employ Web Application Firewalls (WAFs) with rules designed to detect and block malicious serialized payloads targeting fastjson deserialization vulnerabilities.
  3. Monitor application logs and network traffic for unusual or unexpected serialized object patterns indicative of exploitation attempts.
  4. If possible, disable or replace the fastjson library with a safer alternative or upgrade to a version that includes deserialization security fixes.
  5. Implement strict input validation and deserialization filters to reject untrusted or malformed data before processing.
  6. Engage with the vendor for patches or official guidance and apply updates as soon as they become available.
  7. Conduct internal audits to identify all instances of fastjson usage within the ERP and related systems to ensure comprehensive coverage.
  8. Educate development and security teams about deserialization risks and secure coding practices to prevent future vulnerabilities.

Description

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

References

Community reviews

Loading reviews…