# CVE-2025-10277: YunaiV yudao-cloud submit improper authorization

> Remote attackers can bypass authorization checks in the yudao-cloud CRM receivable submission endpoint to modify data without proper permissions.

- **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:** 12 Sep 2025
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-69f2-6mjq-5xcx

## What is CVE-2025-10277?

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

### Official description

A vulnerability was detected in YunaiV yudao-cloud up to 2025.09. This issue affects some unknown processing of the file /crm/receivable/submit. The manipulation of the argument ID results in improper authorization. The attack can be executed remotely. The exploit is now public and may be used. The patch is identified as 0f573e1d8e1a895e1bcbb7740ef75306412c3f9d (master-jdk17). It is best practice to apply a patch to resolve this issue. The vendor confirms: "[W]e have now added the missing per-record CRM WRITE permission check to submitReceivable, the path reported as CVE-2025-10277, in both Boot and Cloud master-jdk17. Possession of a functional submit permission alone no longer permits submission of a record for which the caller lacks CRM write access."

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

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

It affects 1 product.


Products: Iocoder Yudao-Cloud.

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

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

## Is CVE-2025-10277 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10277 exists.

## Other vulnerabilities in YunaiV yudao-cloud

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10277 is a medium-severity missing authorization vulnerability in YunaiV yudao-cloud, published on 12 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10277 exists.

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-10277/ (Markdown: https://insights.sbomify.com/CVE-2025-10277/index.md)
```

## Sources

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

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