# CVE-2025-4537: yangzongzhuan RuoYi-Vue Password login.vue sensitive information in a cookie

> Attackers can retrieve sensitive credentials stored in cleartext cookies from the RuoYi-Vue login interface, potentially leading to account compromise.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 May 2025
- **Updated:** 12 May 2025
- **Also known as:** GHSA-rm2h-h7xf-gvc8

## What is CVE-2025-4537?

CVE-2025-4537 is a low-severity vulnerability in yangzongzhuan RuoYi-Vue, published on 11 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability was found in yangzongzhuan RuoYi-Vue up to 3.8.9 and classified as problematic. Affected by this issue is some unknown functionality of the file ruoyi-ui/jsencrypt.js and ruoyi-ui/login.vue of the component Password Handler. The manipulation leads to cleartext storage of sensitive information in a cookie. The attack may be launched remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used.

Weakness: CWE-315 (Cleartext Storage of Sensitive Information in a Cookie), CWE-312 (Cleartext Storage of Sensitive Information)

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

It affects 1 product.


Products: Ruoyi Ruoyi-Vue.

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

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

## Is CVE-2025-4537 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4537 is a low-severity vulnerability in yangzongzhuan RuoYi-Vue, published on 11 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4537 exists.

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

## Sources

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

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