dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-10152

MEDIUM · 6.3 CVSS v3.1 Published 2026-05-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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 was detected in TaleLin lin-cms-spring-boot up to 0.2.1. This issue affects some unknown processing of the file src/main/java/io/github/talelin/latticy/controller/v1/BookController.java of the component book Endpoint. The manipulation results in improper access controls. The attack may be launched remotely. The exploit is now public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

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 vulnerability exists in the BookController endpoint of lin-cms-spring-boot (versions up to 0.2.1), where improper access controls allow unauthorized users to manipulate book-related operations. The lack of proper authorization checks on the endpoint enables remote attackers to access or modify book data without appropriate permissions.

MitigationImplement proper role-based access control (RBAC) and authorization checks on all BookController endpoints, ensuring users can only access book resources according to their assigned roles and permissions.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 lin-cms-spring-boot version
    Inspect your project's dependency management file (pom.xml, build.gradle, or gradle.lock) for the lin-cms-spring-boot artifact version. Alternatively, list the contents of the deployed WAR/JAR file and search for lin-cms related jars.
    Affected if The reported version is 0.2.1 or lower (including any 0.x.y version below 0.2.1)
  2. Locate BookController.java in the codebase
    Search your source code repository or decompiled application bytecode for a file named BookController.java. If using an IDE, use 'Find in Files' to search for 'class BookController'.
    Affected if BookController.java exists in the deployed application and handles book-related HTTP endpoints (e.g., /book, /books, /api/book/*)
  3. Verify Spring Security configuration on book endpoints
    Examine your Spring Security configuration class (often named SecurityConfig.java or extending WebSecurityConfigurerAdapter). Check if the book endpoints are explicitly secured with permitAll() or have no security rule defined. Look for antMatchers("/book/**").permitAll() or missing antMatchers for book routes.
    Affected if The book endpoints are configured with .permitAll() or are not covered by any security rule (default permit)
  4. Check for authorization annotations on BookController methods
    Open BookController.java and inspect the class and method declarations. Look for @PreAuthorize, @Secured, or method-level security annotations. Check if these annotations are missing or improperly configured (e.g., no role requirements).
    Affected if BookController methods lack @PreAuthorize annotations with proper role requirements, or the defined roles do not restrict access adequately

You are affected if your lin-cms-spring-boot version is 0.2.1 or lower AND the BookController endpoints are accessible without authentication due to missing or misconfigured Spring Security rules.

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 role-based access control (RBAC) and authorization checks on all BookController endpoints, ensuring users can only access book resources according to their assigned roles and permissions.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10152 — 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-2026-10152 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