dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-10439

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Yordam Informatics Yordam Library Automation System allows SQL Injection. This issue affects Yordam Library Automation System: from 21.5 & 21.6 before 21.7.

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

SQL injection vulnerability in Yordam Library Automation System versions 21.5 and 21.6 allows attackers to inject malicious SQL queries through unsanitized user input. The improper neutralization of special elements in SQL commands enables remote attackers to execute arbitrary SQL statements against the database.

MitigationUpgrade Yordam Library Automation System to version 21.7 or later to obtain the patched version. If immediate upgrade is not possible, implement input validation and parameterized queries as temporary mitigations.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Confirm Yordam Library Automation System is present
    Check if the application is accessible by visiting the web interface, checking HTTP headers for 'Yordam' or 'Library Automation', or looking for Yordam-related processes or services on the server
    Affected if The system is running Yordam Library Automation System
  2. Identify the installed version
    Navigate to the admin panel, 'About' page, or check configuration files (such as web.config, app.config, or version manifests in the installation directory) to find the exact version number
    Affected if The version is 21.5 or 21.6
  3. Verify the system is network-accessible
    Confirm that the web interface is exposed on an accessible network port (HTTP/HTTPS) and reachable from potential attacker locations
    Affected if The application is accessible remotely without proper network segmentation
  4. Check for unauthenticated query parameters
    Inspect the application's login, search, or other input forms by examining the HTML source or intercepting requests to identify query parameters that may be passed to SQL queries without proper sanitization
    Affected if User-supplied input fields are used in SQL queries without parameterized queries or input validation

A user is affected if Yordam Library Automation System versions 21.5 or 21.6 are running and accessible, with user input being passed directly to SQL queries.

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 Yordam Library Automation System to version 21.7 or later to obtain the patched version. If immediate upgrade is not possible, implement input validation and parameterized queries as temporary mitigations.

Recommended fix Moderate confidence

Yordam Library Automation System version 21.7

  1. 1. Create a full backup of the current Yordam Library Automation System database and configuration files
  2. 2. Obtain the version 21.7 release of Yordam Library Automation System from the official Yordam Informatics vendor
  3. 3. Follow the vendor's official upgrade documentation to install version 21.7
  4. 4. After upgrade, verify the application is functioning correctly and the SQL injection vulnerability is resolved
  5. 5. Test that all library operations (user management, book catalog, circulation) work as expected post-upgrade
Caveat Review vendor release notes for version 21.7 to check for any changes to existing functionality or required configuration adjustments

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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