dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2025-2686

MEDIUM · 6.5 CVSS v3.1 Published 2025-03-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The library management system 'mingyuefusu tushuguanlixitong' contains an improper access control vulnerability in the Backend component's doFilter function at the /admin/ endpoint. The vulnerability allows remote attackers to bypass authentication by manipulating the Request argument, potentially gaining unauthorized administrative access to the system.

MitigationImplement proper authentication and authorization checks in the doFilter function to validate user sessions and role-based access before granting access to admin endpoints. Ensure all sensitive endpoints enforce role verification.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if the mingyuefusu tushuguanlixitong library management system is running
    Check running web services or application processes on the server that match this library management system. Look for processes listening on web ports (80, 443, 8080, etc.) that serve this application.
    Affected if The system is running and exposes the /admin/ endpoint on the network.
  2. Verify the /admin/ endpoint exists and is reachable
    Attempt to access the /admin/ endpoint via HTTP/HTTPS request without providing credentials. Use a tool like curl: curl -I http://[target]/admin/ or https://[target]/admin/
    Affected if The endpoint responds with any HTTP status code (200, 401, 403, 302 redirect) indicating the endpoint is accessible.
  3. Inspect the doFilter function in the Backend component
    Locate the application source code or configuration files. Find the doFilter function within the filter chain (typically in Java web applications in files like FilterChain.java, SecurityFilter.java, or similar). Examine how it handles authentication for /admin/ paths.
    Affected if The doFilter function does not perform proper session validation or role-based access control checks before allowing access to /admin/ endpoints.
  4. Check Request argument handling for authentication bypass
    Review the doFilter code to see if user-controlled Request parameters (such as headers, cookies, or query parameters) can influence authentication decisions. Look for logic that checks Request attributes without validating them against a trusted session store.
    Affected if The code accepts authentication tokens or session identifiers directly from the Request without verifying them against a server-side session store.
  5. Test for authentication bypass via Request manipulation
    Send requests to /admin/ with modified Request headers or parameters (such as X-Admin-User: 1, or cookie manipulation) without valid credentials. Compare the response to an unauthenticated request.
    Affected if Requests with manipulated Request arguments gain access to admin functionality that should require authentication.

A user is affected if the mingyuefusu tushuguanlixitong system is running with the /admin/ endpoint accessible and the doFilter function allows authentication bypass via Request argument manipulation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authentication and authorization checks in the doFilter function to validate user sessions and role-based access before granting access to admin endpoints. Ensure all sensitive endpoints enforce role verification.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2686 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-2686 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data