dbcve.org
Library Automation SystemApplication · Yordam

CVE-2021-45479

MEDIUM · 5.4 CVSS v3.1 Published 2023-03-02
Fix available
A fix is available. Upgrade to 19.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Input During Web Page Generation vulnerability in Yordam Information Technologies Library Automation System allows Stored XSS. This issue affects Library Automation System: before 19.2.

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

Stored XSS vulnerability in Yordam Library Automation System allows authenticated attackers to inject malicious JavaScript code into web input fields (such as search, user profiles, or catalog entries). When other users view the affected pages, the injected scripts execute in their browsers, enabling session hijacking, credential theft, or defacement.

MitigationUpdate to version 19.2 or later which contains the patch. If immediate update is not possible, implement output encoding and input validation on all user-facing fields, and consider Content Security Policy headers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Library Automation SystemApplication
Affected:< 19.2

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 in use
    Identify the web application by checking the login page, header, or footer for 'Yordam' branding. Look at the application URL patterns or examine the HTML source for 'yordam' references.
    Affected if The application running is Yordam Library Automation System
  2. Determine the installed version
    Access the admin panel, 'Hakkında' (About), or system information page. Check the footer for version numbers. Look in configuration files or the database for version metadata if accessible.
    Affected if The installed version is below 19.2 (for example, 19.1, 18.x, or earlier)
  3. Verify web interface is accessible
    Attempt to access the application's web login page via browser. Confirm the system is actively serving HTTP/HTTPS requests.
    Affected if The web interface is exposed and reachable on the network
  4. Identify user input fields
    Navigate to the search function, user profile editor, and catalog entry forms. Note all text input fields, textareas, and form submission points.
    Affected if User-controllable input fields exist in search, profile, or catalog sections
  5. Check if authentication is configured
    Determine whether the system requires login for access. Try accessing protected pages without credentials to see if authentication is enforced.
    Affected if Authentication is enabled, which is required for attackers to exploit the stored XSS (attackers must be authenticated users)

You are affected if Yordam Library Automation System is running with a version below 19.2 and the web interface with user input fields is accessible to authenticated users.

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
Upgrade available Upgrade to 19.2 or later
Fixed in 19.2
Interim mitigation

Update to version 19.2 or later which contains the patch. If immediate update is not possible, implement output encoding and input validation on all user-facing fields, and consider Content Security Policy headers.

Recommended fix Moderate confidence

19.2

  1. 1. Verify current installation of Yordam Library Automation System by checking the version number in the administration panel or system configuration.
  2. 2. Back up the entire system including database, configuration files, and custom templates before proceeding with any upgrade.
  3. 3. Download the version 19.2 release package from the official vendor (Yordam Information Technologies) or authorized distribution channels.
  4. 4. Review the upgrade documentation provided with version 19.2 for any specific migration procedures or prerequisites.
  5. 5. Execute the upgrade process following the vendor's prescribed upgrade methodology, which typically involves running the installer or migration script.
  6. 6. After upgrade completion, verify that the system is operational and all core functionalities are working correctly.
  7. 7. Confirm that the installed version is now 19.2 by checking the system information or about page.
  8. 8. Test the previously vulnerable areas to confirm the XSS vulnerability has been remediated.

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

Fix this in Library Automation System 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 the upgrade done

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-2021-45479 — 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-2021-45479 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