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

> Attackers can bypass UI restrictions to perform privileged operations and access sensitive data due to desynchronized backend permission checks.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Dec 2025
- **Updated:** 8 Dec 2025
- **Also known as:** GHSA-2w5f-22g3-8h49

## What is CVE-2025-55948?

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

### Official description

This vulnerability fundamentally arises from yzcheng90 X-SpringBoot 6.0's implementation of role-based access control (RBAC) through dual dependency on frontend menu systems and backend permission tables, without enforcing atomic synchronization between these components. The critical flaw manifests when frontend menu updates (such as privilege revocation) fail to propagate to the backend permission table in real-time, creating a dangerous desynchronization. While users lose access to restricted functions through the web interface (as UI elements properly disappear), the stale permission records still validate unauthorized API requests when accessed directly through tools like Postman. Attackers exploiting this inconsistency can perform privileged operations including but not limited to: creating high-permission user accounts, accessing sensitive data beyond their clearance level, and executing admin-level commands.

Weakness: CWE-266 (Incorrect Privilege Assignment)

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

It affects 1 product.


Products: Yzcheng90 X-Springboot.

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

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

## Is CVE-2025-55948 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-55948 is a high-severity missing authorization vulnerability in n/a, published on 4 Dec 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-55948 exists.

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

## Sources

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

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