dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2025-15023

HIGH · 8.8 CVSS v3.1 Published 2026-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Incorrect Authorization vulnerability in Yordam Information Technology Consulting, Training and Electronic Systems Industry and Trade Inc. Library Automation System allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects Library Automation System: from v.19.5 before v.22.1.

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

This is an incorrect authorization vulnerability in Yordam Library Automation System where access control security levels are misconfigured. The flaw allows attackers to exploit improperly configured security levels to gain unauthorized access to system functions or data that should be restricted.

MitigationUpgrade the Library Automation System to version 22.1 or later, which contains the fix for the incorrectly configured access control security levels.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 Yordam Library Automation System is installed
    Locate the Yordam Library Automation System installation directory or check system inventory/registry for this product
    Affected if The product is installed on the system
  2. Determine the installed version of Yordam Library Automation System
    Check the application version through its about dialog, installation folder metadata, or system configuration where the version is recorded
    Affected if The installed version is earlier than 22.1
  3. Examine access control security level configuration
    Locate and inspect the security configuration file, user permission settings, or role-based access control definitions within the application
    Affected if Security levels are set to allow broader access than intended or misconfigured compared to expected restricted settings
  4. Verify if unauthorized access to restricted functions is possible
    Test or inspect whether users with lower security clearance can access functions or data that should be restricted based on the security level settings
    Affected if Users can access functions or data outside their intended security level scope
  5. Compare against the fixed version threshold
    Document the current version and confirm whether it is below 22.1
    Affected if The installed version is below 22.1 and the security configuration shows misconfigured access control levels

A system is affected if Yordam Library Automation System is installed with a version earlier than 22.1 and has misconfigured access control security levels that allow unauthorized access to restricted functions or data.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the Library Automation System to version 22.1 or later, which contains the fix for the incorrectly configured access control security levels.

Recommended fix High confidence

v.22.1 or later

  1. Ensure you have a complete backup of the current Library Automation System database and configuration files before proceeding.
  2. Obtain the fixed version v.22.1 or later of the Yordam Library Automation System from the vendor.
  3. Follow the vendor's documented upgrade procedure to migrate from the current version (v.19.5 through v.22.0) to v.22.1 or later.
  4. After upgrade, verify that the access control security levels are properly configured and the Incorrect Authorization vulnerability is remediated.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,790
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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