# CVE-2026-116015: yudao-cloud through 2026.09 IDOR via after-sale-log list endpoint


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-3pvc-3977-gxh7

## What is CVE-2026-116015?

CVE-2026-116015 is a medium-severity vulnerability in YunaiV yudao-cloud, published on 24 Oct 2026. 

### Official description

yudao-cloud through 2026.09 contains an insecure direct object reference vulnerability in the mall trade module that allows authenticated members to read other members' after-sale operation logs by supplying arbitrary afterSaleId values. Attackers can enumerate sequential after-sale IDs against GET /app-api/trade/after-sale-log/list to expose refund amounts, status transitions and timestamps belonging to other members.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-116015?


## How do I fix CVE-2026-116015?

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

## Is CVE-2026-116015 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-116015 and fix it if it is affected.

What it is: CVE-2026-116015 is a medium-severity vulnerability in YunaiV yudao-cloud, published on 24 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116015 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-2026-116015/ (Markdown: https://insights.sbomify.com/CVE-2026-116015/index.md)
```

## Sources

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

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