dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-15024

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
Improper Control of Generation of Code ('Code Injection') vulnerability in Yordam Information Technology Consulting, Training and Electronic Systems Industry and Trade Inc. Library Automation System allows Remote Code Inclusion. 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 · high confidence

This is a code injection vulnerability in Yordam's Library Automation System that allows remote code inclusion. The vulnerability exists in versions from v.19.5 before v.22.1, likely due to insufficient validation of user-supplied input used in file inclusion operations. An attacker could exploit this to include malicious remote files and execute arbitrary code on the server.

MitigationUpgrade to Library Automation System v.22.1 or later which contains the fix. If immediate patching is not possible, disable or restrict remote file inclusion capabilities and implement strict input validation on any file inclusion logic.

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
    Check for the application in common installation directories or look for running processes named 'yordam' or 'library-automation'. Use commands like 'ps aux | grep -i yordam' on Linux or check installed programs on Windows.
    Affected if The application is present on the system
  2. Determine the installed version
    Locate the version information file or check the application about page. Common locations include: version.txt, VERSION file in the installation root, or the admin dashboard. Compare the version number against the affected range: v.19.5 and later but before v.22.1.
    Affected if The installed version is 19.5 or later but earlier than 22.1
  3. Locate file inclusion configuration settings
    Examine the application's configuration files for settings related to file inclusion, remote file inclusion, or dynamic loading. Look for parameters named 'allow_url_include', 'file_include', 'remote_include', or similar in config files.
    Affected if Remote file inclusion settings are found and enabled in the configuration
  4. Inspect the file inclusion code logic
    Review the source code or decompiled classes responsible for file inclusion operations. Look for include(), require(), or similar functions that use user-supplied input without proper validation. Check if the input passes through sanitization before being used in file operations.
    Affected if The code uses unsanitized user input in file inclusion functions
  5. Check for exposed file inclusion endpoints
    If the application has a web interface, probe common endpoints that might handle file paths (e.g., ?page=, ?file=, ?include=). Observe if the application attempts to load external resources based on user input.
    Affected if User-controllable parameters can influence file inclusion paths

A system is affected if it runs Yordam Library Automation System version 19.5 or later but earlier than 22.1 AND has remote file inclusion capabilities enabled or accessible via web input parameters.

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 which contains the fix. If immediate patching is not possible, disable or restrict remote file inclusion capabilities and implement strict input validation on any file inclusion logic.

Recommended fix Moderate confidence

v.22.1

  1. Obtain the v.22.1 release of Yordam Library Automation System from the official vendor (Yordam Information Technology Consulting, Training and Electronic Systems Industry and Trade Inc.)
  2. Back up the current database and configuration files before performing the upgrade
  3. Deploy v.22.1 in a staging environment to verify compatibility with existing integrations
  4. Apply the upgrade to the production environment following the vendor's standard upgrade procedure
  5. Verify that the application functions correctly after the upgrade
  6. Confirm the vulnerability is remediated by testing that remote code inclusion is no longer possible
Caveat Review v.22.1 release notes for any breaking changes or deprecations compared to your current version before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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