# CVE-2025-66735: Missing authorization in n/a

> Non-root users can access root roles due to missing permission checks in the role form retrieval function, leading to privilege escalation.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Dec 2025
- **Updated:** 22 Dec 2025
- **Also known as:** GHSA-vfjq-wcxg-p5r3

## What is CVE-2025-66735?

CVE-2025-66735 is a high-severity missing authorization vulnerability in n/a, published on 22 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

youlai-boot V2.21.1 is vulnerable to Incorrect Access Control. The getRoleForm function in SysRoleController.java does not perform permission checks, which may allow non-root users to directly access root roles.

Weakness: CWE-862 (Missing Authorization), CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Youlai Youlai-Boot.

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

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

## Is CVE-2025-66735 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-55469](https://insights.sbomify.com/CVE-2025-55469/): Privilege escalation in n/a (critical 9.8)
- [CVE-2025-55471](https://insights.sbomify.com/CVE-2025-55471/): Missing authorization in n/a (high 7.5)
- [CVE-2025-66736](https://insights.sbomify.com/CVE-2025-66736/): Missing authorization in n/a (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-66735 is a high-severity missing authorization vulnerability in n/a, published on 22 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-66735 in the wild and no public exploit code.

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

## Sources

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

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