CVE-2025-51744
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered in jishenghua JSH_ERP 2.3.1. The /user/addUser endpoint is vulnerable to fastjson deserialization attacks.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe /user/addUser endpoint in JSH_ERP 2.3.1 accepts JSON input that is parsed by the fastjson library, which is vulnerable to deserialization attacks allowing remote code execution. An unauthenticated attacker can send specially crafted JSON payloads to execute arbitrary code on the server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2.3.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify JSH_ERP versionLocate the version file or check build configuration: look for version.properties, pom.xml, build.gradle, or application manifest files in the JSH_ERP deployment directory. The version is typically found in a version.txt file or the JAR/WAR manifest.Affected if The installed version is Jishenghua Jsherp version 2.3.1 or lower.
-
Confirm fastjson library presenceSearch the application lib or lib folder for fastjson JAR files (fastjson.jar, fastjson-1.x.jar, fastjson-2.x.jar). Also check pom.xml or build.gradle dependencies for com.alibaba:fastjson entries.Affected if The fastjson library (particularly fastjson 1.x) is included in the application dependencies.
-
Verify /user/addUser endpoint existsInspect the controller source code or decompile the application JAR/WAR. Look for a UserController or similar class with a mapping for /user/addUser. Check web.xml or the application's routing configuration.Affected if The /user/addUser endpoint is exposed and accessible without authentication.
-
Check fastjson autoType settingExamine the application configuration files (application.properties, application.yml) and initialization code for fastjson settings. Look for features.ParserConfig.autoTypeSupport or fastjson serializer features configuration.Affected if fastjson autoType is explicitly enabled (set to true) or not explicitly disabled, which allows deserialization of arbitrary classes.
A user is affected if they are running JSH_ERP version 2.3.1 or lower with fastjson library present and the /user/addUser endpoint exposed, especially if fastjson autoType is not disabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade fastjson to the latest patched version (preferably fastjson2) or replace fastjson with a secure alternative like Jackson or Gson, then validate the /user/addUser endpoint no longer accepts malicious deserialization payloads.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-51744 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-51744 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data