Severity:

HIGH RISK

(7.3)

Improper Access Control in BookController of LibrarySystem

CVE-2026-2549

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-266, CWE-284

Impact:

Unauthorized Access and Operations on Library Resources

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

LibrarySystem 图书馆管理系统 up to version 1.1.1 contains an access control flaw in BookController.java that allows certain operations on book resources to be performed without proper authorization checks.

A remote attacker can abuse this missing or weak authorization to access or manipulate data or actions that should be restricted, especially when the application is exposed over the network.

Affected context

The vulnerability occurs in the BookController component of the LibrarySystem 图书馆管理系统 application (versions up to 1.1.1).

It affects deployments where:

  • The application is accessible over a network (e.g., internet or intranet)
  • Book-related endpoints are reachable without strong authentication/authorization enforcement
  • The controller relies on implicit trust of client requests or weak role checks

Because the exact function is unspecified, any book management actions exposed by BookController (such as viewing, modifying, or deleting records) may be at risk.

Exploit preconditions

  • Attack surface: Network-exposed HTTP endpoints handled by BookController.java
  • Required access: Remote access to the application; no or low-privilege authentication may be sufficient depending on configuration
  • Trigger point: Sending crafted HTTP requests to vulnerable BookController routes that lack robust authorization checks
  • Why exploitation is possible: The controller does not reliably verify whether the caller is permitted to perform the requested operation, leading to improper access control (CWE-284) and incorrect privilege assignment or enforcement (CWE-266)

Why this happens

The underlying issue is an authorization logic flaw in the BookController that either omits or misconfigures access control checks on certain operations.

Instead of enforcing fine-grained permissions based on authenticated identity and role, the controller appears to:

  • Trust that any caller reaching the endpoint is allowed to perform the action, or
  • Apply overly broad roles or insecure default permissions

This maps to CWE-284: Improper Access Control and CWE-266: Incorrect Privilege Assignment, where privilege boundaries are not correctly enforced, allowing users to access resources or actions beyond their intended permissions.

Potential impact

  • Unauthorized viewing of book or related metadata that should be restricted
  • Unauthorized modification or deletion of book records
  • Creation of fraudulent or tampered entries in the library system
  • Indirect exposure or corruption of linked data (e.g., circulation or inventory information)
  • Potential stepping stone for broader account or system misuse depending on the surrounding application logic

General mitigation guidance

Effective mitigation focuses on introducing or strengthening explicit authorization checks for all BookController endpoints:

  • Apply a central, consistent authorization mechanism (e.g., role-based or attribute-based access control) for every controller action
  • Use secure-by-default access policies, treating all operations as denied unless explicitly allowed to specific roles
  • Separate responsibilities so that read, write, and administrative operations have distinct, minimal roles
  • Avoid relying on client-supplied parameters (e.g., user IDs or roles) to determine access; derive authorization solely from server-side session or token data
  • Implement and document a clear permission model for book management and enforce it uniformly across controllers and services

These measures reduce the chance that new endpoints will inherit insecure defaults or bypass authorization unintentionally.

How teams detect issues like this

To detect similar access control weaknesses:

  • Perform static analysis to flag controller methods missing explicit authorization annotations or checks
  • Use code review checklists that require reviewers to confirm access control for every externally reachable endpoint
  • Implement security tests that attempt restricted actions with low-privilege or unauthenticated accounts, validating that access is denied
  • Employ application-level logging and monitoring that highlight unusual access patterns (e.g., low-privilege users invoking administrative-looking operations)
  • Integrate automated policy enforcement tools into CI/CD pipelines to detect endpoints that do not conform to required authorization patterns

Sources

SourceLink
github.comgithub.com/zhanghuanhao/LibrarySystem/issues/32
github.comgithub.com/zhanghuanhao/LibrarySystem/issues/32#issue-3879640487
vuldb.comvuldb.com/?ctiid.346158
vuldb.comvuldb.com/?id.346158
vuldb.comvuldb.com/?submit.749873

Frequently asked

questions

Yes. The affected BookController endpoints can be reached over the network, so a remote attacker can exploit the issue wherever the application is exposed.

Not necessarily. Depending on how the instance is configured, exploitation may be possible without authentication or with a low-privilege account, because the core problem is insufficient authorization on the controller actions.

Introduce strict, explicit authorization checks on all BookController operations, following a deny-by-default model and enforcing least privilege for each action (view, create, update, delete).

Define a clear access control model early, enforce it through centralized authorization mechanisms and annotations, require security-focused code reviews, and use automated checks to ensure that new endpoints cannot be added without appropriate authorization controls.

Find out what's already
exploitable in your codebase.