# CVE-2025-0734: y_project RuoYi Whitelist getBeanName deserialization

> Remote attackers can achieve code execution via unsafe deserialization in the RuoYi Whitelist getBeanName function.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jan 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-w8g9-387p-pmg5

## What is CVE-2025-0734?

CVE-2025-0734 is a medium-severity unsafe deserialization vulnerability in Ruoyi Ruoyi, published on 27 Jan 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability has been found in y_project RuoYi up to 4.8.0 and classified as critical. This vulnerability affects the function getBeanName of the component Whitelist. The manipulation leads to deserialization. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-502 (Deserialization of Untrusted Data), CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Ruoyi Ruoyi.

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

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

## Is CVE-2025-0734 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-0734 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-0734 and fix it if it is affected.

What it is: CVE-2025-0734 is a medium-severity unsafe deserialization vulnerability in Ruoyi Ruoyi, published on 27 Jan 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-0734 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-0734/ (Markdown: https://insights.sbomify.com/CVE-2025-0734/index.md)
```

## Sources

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

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