CVE-2025-10987
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 · uneditedA vulnerability was determined in YunaiV yudao-cloud up to 2025.09. Affected by this issue is some unknown functionality of the file /crm/contact/transfer of the component HTTP Request Handler. This manipulation of the argument contactId causes improper authorization. It is possible to initiate the attack remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.
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 · moderate confidenceYunaiV yudao-cloud up to 2025.09 contains an improper authorization vulnerability in the /crm/contact/transfer endpoint. Attackers can manipulate the contactId parameter to bypass authorization checks and potentially transfer contacts they should not have access to. The attack is exploitable remotely and public exploits exist.
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<= 2025.09CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 installed Yudao Cloud versionCheck the application's version information in the admin panel under 'System Management > System Settings' or examine the build configuration files (pom.xml, application.yml) in the deployment directory for the version identifier.Affected if The installed version is 2025.09 or any version up to and including 2025.09.
-
Verify /crm/contact/transfer endpoint existsAccess the API endpoint at /crm/contact/transfer (or /crm/contact/transfer via web UI) using HTTP methods (GET/POST). Check if the endpoint responds to requests, indicating it is enabled in the application.Affected if The endpoint returns any HTTP response (200, 403, 500, etc.) rather than a 404, confirming the endpoint is exposed.
-
Confirm CRM contact module is enabledNavigate to the CRM module in the Yudao Cloud admin interface and verify that the 'Contact Management' feature is active. Alternatively, check the database or configuration for crm.contact.enabled=true or similar flags.Affected if The CRM contact module is enabled and accessible to the authenticated user.
-
Test authorization on contact transfer operationLog in as a standard user with limited permissions, then attempt to access the transfer endpoint with a contactId belonging to a different user or department. Observe whether the request succeeds or is properly rejected with 403 Forbidden.Affected if The request succeeds or returns data for a contact the authenticated user does not own, indicating broken authorization.
You are affected if your Yudao Cloud version is 2025.09 or earlier, the /crm/contact/transfer endpoint is accessible, and unauthorized users can transfer contacts they do not own.
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 dataImplement proper authorization checks on the contact transfer endpoint, validating that the authenticated user has rights to transfer the specific contactId being requested. Until vendor patch is available, consider API gateway-level authorization controls or network segmentation as compensating controls.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10987 — 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-10987 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