# CVE-2025-10384: yangzongzhuan RuoYi Role cancelAll improper authorization

> Remote attackers can bypass authorization checks in the Role Handler to modify user role assignments, requiring immediate mitigation due to lack of vendor response.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/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:** 13 Sep 2025
- **Updated:** 15 Sep 2025
- **Also known as:** GHSA-rcg6-pw8r-pvqr

## What is CVE-2025-10384?

CVE-2025-10384 is a medium-severity missing authorization vulnerability in Ruoyi Ruoyi, published on 13 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw has been found in yangzongzhuan RuoYi up to 4.8.1. Affected by this vulnerability is an unknown functionality of the file /system/role/authUser/cancelAll of the component Role Handler. Executing manipulation of the argument roleId/userIds can lead to improper authorization. The attack may be performed from remote. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

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

It affects 1 product.


Products: Ruoyi Ruoyi.

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

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

## Is CVE-2025-10384 being exploited?

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

## Other vulnerabilities in Ruoyi Ruoyi

- [CVE-2024-57521](https://insights.sbomify.com/CVE-2024-57521/): SQL injection in n/a (critical 10.0)
- [CVE-2025-28402](https://insights.sbomify.com/CVE-2025-28402/): Privilege escalation in n/a (critical 9.8)
- [CVE-2025-28405](https://insights.sbomify.com/CVE-2025-28405/): Privilege escalation in n/a (critical 9.8)
- [CVE-2025-28406](https://insights.sbomify.com/CVE-2025-28406/): Privilege escalation in n/a (critical 9.8)
- [CVE-2025-28408](https://insights.sbomify.com/CVE-2025-28408/): Missing authorization in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10384 is a medium-severity missing authorization vulnerability in Ruoyi Ruoyi, published on 13 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-10384 in the wild and no public exploit code.

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

## Sources

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

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