# CVE-2025-28413: Privilege escalation in n/a

> Remote attackers can escalate privileges in the RuoYi admin framework via the SysDictTypeController component.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Apr 2025
- **Updated:** 8 Apr 2025
- **Also known as:** GHSA-3pxq-xg4j-rgqx

## What is CVE-2025-28413?

CVE-2025-28413 is a critical vulnerability in Ruoyi Ruoyi, published on 7 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in RUoYi v.4.8.0 allows a remote attacker to escalate privileges via the SysDictTypeController component

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Ruoyi Ruoyi.

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

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

## Is CVE-2025-28413 being exploited?

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

## 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-28413 and fix it if it is affected.

What it is: CVE-2025-28413 is a critical vulnerability in Ruoyi Ruoyi, published on 7 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-28413 exists.

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

## Sources

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

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