# CVE-2026-57950: ruoyi-vue-pro - Incorrect Permission Namespace in ErpSaleOrderController

> Attackers with shipment permissions can unauthorizedly read, create, update, and delete sale orders due to incorrect permission namespace enforcement.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **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:** 29 Jun 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-r39c-vf2w-53j7

## What is CVE-2026-57950?

CVE-2026-57950 is a high-severity missing authorization vulnerability in Yunai ruoyi-vue-pro, published on 29 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ruoyi-vue-pro through 2026.05, fixed in commit 5d1fd70 contains a broken access control vulnerability in ErpSaleOrderController that allows attackers with erp:sale-out permissions to gain unauthorized access to sale order operations by exploiting an incorrect permission namespace enforcement. Attackers holding shipment-level permissions can perform unauthorized create, update, delete, and read operations on financially sensitive sale orders due to the controller enforcing erp:sale-out instead of the intended erp:sale-order namespace.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-57950 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-57950 is a high-severity missing authorization vulnerability in Yunai ruoyi-vue-pro, published on 29 Jun 2026. 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-2026-57950 exists.

Affected product: Yunai ruoyi-vue-pro. 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-57950/ (Markdown: https://insights.sbomify.com/CVE-2026-57950/index.md)
```

## Sources

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

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