CVE-2025-51745
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 /role/addcan 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 /role/addcan endpoint in jishenghua JSH_ERP 2.3.1 accepts JSON input that is processed by the fastjson library. The endpoint is vulnerable to deserialization attacks where specially crafted JSON payloads can trigger unsafe deserialization, leading to remote code execution. An unauthenticated attacker can exploit this to execute arbitrary commands 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 installationLocate the JSH_ERP application files, running Java process, or web application archive. Check application directories, deployed WAR files, or running services for JSH_ERP.Affected if JSH_ERP is present and running in the environment
-
Verify JSH_ERP versionCheck the installed version of JSH_ERP by inspecting application metadata files (such as version manifests, pom.xml, or the application banner at startup). Compare against the affected range: any version <= 2.3.1Affected if Installed version is 2.3.1 or lower
-
Confirm fastjson library usageInspect the application classpath, lib directory, or build dependencies for the fastjson library. Identify the fastjson version in use.Affected if fastjson library is present in the application dependencies
-
Verify endpoint exposureCheck if the /role/addcan endpoint is accessible by reviewing application routing configuration or by attempting to access the endpoint (if safe to do so).Affected if The /role/addcan endpoint is exposed and reachable
-
Check authentication requirementReview application security configuration to determine if /role/addcan requires authentication, or test the endpoint with an unauthenticated request.Affected if The endpoint accepts requests without authentication
The environment is affected if JSH_ERP version 2.3.1 or lower is installed, the application uses the fastjson library, and the /role/addcan endpoint is exposed without authentication requirements.
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 a patched version (or migrate to a safer JSON library like Jackson or Gson) and restrict network access to the vulnerable endpoint until patched.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-51745 — 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-51745 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