dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-15025

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
Authorization bypass through User-Controlled key vulnerability in Yordam Information Technology Consulting, Training and Electronic Systems Industry and Trade Inc. Library Automation System allows Exploitation of Trusted Identifiers. This issue affects Library Automation System: from v.21.6 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 authorization bypass vulnerability in Yordam Library Automation System where the application uses user-controllable input as a key for authorization decisions. An attacker can manipulate trusted identifiers (such as session tokens, user ID parameters, or other security-relevant data) to bypass authentication and access unauthorized resources or functionality. The vulnerability exists in versions v.21.6 through v.22.0 and is fixed in v.22.1.

MitigationUpgrade to Library Automation System v.22.1 or later. Additionally, review all code paths where user-controlled input is used for authorization decisions and implement proper server-side validation that doesn't rely on trusted client-side identifiers.

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 installed Yordam Library Automation System version
    Check the application version through the admin interface, about page, or configuration files (typically in installation directory or database). Compare against the fixed version v.22.1.
    Affected if Running any version prior to v.22.1 indicates potential vulnerability.
  2. Locate API endpoints or functions accepting user-supplied identifiers
    Review application source code or API documentation for parameters that accept keys, IDs, tokens, or other identifiers directly from client requests without server-side generation or validation.
    Affected if Endpoints accept and trust client-provided identifier values for authorization decisions.
  3. Inspect authorization logic for client-controlled key usage
    Search code for authorization checks that use request parameters (query strings, headers, body fields) as trusted identifiers without validating them against server-side session or permission records.
    Affected if Authorization logic relies on user-controllable parameters to determine access rights.
  4. Test for parameter manipulation on restricted functions
    Identify protected functions (admin operations, user data access, circulation records) and attempt to modify identifier parameters in requests to access unauthorized resources.
    Affected if Modifying identifier values allows access to data or functions outside the user's legitimate scope.
  5. Review session and token handling implementation
    Examine how the application manages session tokens, API keys, or authentication credentials. Verify if these are server-generated and validated, not client-supplied values used directly.
    Affected if Application accepts client-specified keys/IDs as valid authentication without server-side verification.

If running Yordam Library Automation System versions before v.22.1 and the application trusts client-supplied identifiers for authorization, the environment is vulnerable to CVE-2025-15025.

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 to Library Automation System v.22.1 or later. Additionally, review all code paths where user-controlled input is used for authorization decisions and implement proper server-side validation that doesn't rely on trusted client-side identifiers.

Recommended fix Moderate confidence

v.22.1

  1. Backup the current Library Automation System database and configuration files before proceeding with any upgrade.
  2. Verify the current installed version is between v.21.6 and v.22.0 using the system's version check (typically available in admin panel or system information page).
  3. Obtain the v.22.1 release package from the official vendor (Yordam Information Technology Consulting, Training and Electronic Systems Industry and Trade Inc.).
  4. Follow the vendor's standard upgrade procedure for the Library Automation System, which typically includes: stopping the application services, replacing the application files, running any database migration scripts if provided, and restarting services.
  5. After upgrade, verify the system is running v.22.1 and confirm that the IDOR vulnerability is resolved by testing that unauthorized access to other users' records/identifiers is now properly restricted.
  6. Test core library operations (circulation, cataloging, user management) to ensure functionality is intact post-upgrade.
Caveat Review vendor release notes for v.22.1 to check for any breaking changes or deprecated features that may affect existing workflows or integrations.

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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