# CVE-2025-10987: YunaiV yudao-cloud HTTP Request transfer improper authorization

> Attackers can improperly transfer CRM contacts by bypassing authorization checks in the HTTP request handler.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2025
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-qw2g-qp82-qw5p

## What is CVE-2025-10987?

CVE-2025-10987 is a medium-severity missing authorization vulnerability in YunaiV yudao-cloud, published on 26 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A 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 affected component should be upgraded. The vendor confirms: "The controllers check the relevant update permission and obtain the acting user ID from the authenticated server context. The services require CRM OWNER permission and call transferPermission, which explicitly rejects a caller who is neither the owner nor an authorized CRM administrator."

Weakness: CWE-285 (Improper Authorization), CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2025-10987?

It affects 1 product.


Products: Iocoder Yudao-Cloud.

## How do I fix CVE-2025-10987?

No fix has been published for CVE-2025-10987 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-10987 being exploited?

There is no known exploitation of CVE-2025-10987 in the wild and no public exploit code.

## Other vulnerabilities in YunaiV yudao-cloud

- [CVE-2025-10275](https://insights.sbomify.com/CVE-2025-10275/): YunaiV yudao-cloud transfer improper authorization (medium 5.3)
- [CVE-2025-10277](https://insights.sbomify.com/CVE-2025-10277/): YunaiV yudao-cloud submit improper authorization (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10987 and fix it if it is affected.

What it is: CVE-2025-10987 is a medium-severity missing authorization vulnerability in YunaiV yudao-cloud, published on 26 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-10987 in the wild and no public exploit code.

Affected product: YunaiV yudao-cloud. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-10987/ (Markdown: https://insights.sbomify.com/CVE-2025-10987/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-10987
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-10987
- OSV: https://osv.dev/vulnerability/CVE-2025-10987

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-10987/
Summaries are generated and may contain mistakes; the official description above is the record.