# CVE-2025-2686: mingyuefusu 明月复苏 tushuguanlixitong 图书管理系统 Backend admin doFilter access control

> Remote attackers can bypass backend admin access controls in the library management system to gain unauthorized privileges.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Mar 2025
- **Updated:** 24 Mar 2025
- **Also known as:** GHSA-pqpp-cgm6-hx6c

## What is CVE-2025-2686?

CVE-2025-2686 is a medium-severity missing authorization vulnerability in mingyuefusu 明月复苏 tushuguanlixitong 图书管理系统, published on 24 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been found in mingyuefusu 明月复苏 tushuguanlixitong 图书管理系统 up to d4836f6b49cd0ac79a4021b15ce99ff7229d4694 and classified as critical. Affected by this vulnerability is the function doFilter of the file /admin/ of the component Backend. The manipulation of the argument Request leads to improper access controls. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-284 (Improper Access Control), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2025-2686 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2686 is a medium-severity missing authorization vulnerability in mingyuefusu 明月复苏 tushuguanlixitong 图书管理系统, published on 24 Mar 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-2686 exists.

Affected product: mingyuefusu 明月复苏 tushuguanlixitong 图书管理系统. 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-2686/ (Markdown: https://insights.sbomify.com/CVE-2025-2686/index.md)
```

## Sources

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

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