CVE-2025-1301
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 · uneditedImproper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Yordam Informatics Library Automation System allows Reflected XSS. This issue affects Library Automation System: before 21.6.
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 confidenceReflected XSS vulnerability in Yordam Informatics Library Automation System allows attackers to inject malicious scripts through unsanitized user input that gets reflected back in web page responses.
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< 21.6CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Yordam Library Automation System versionLocate the version information in the system's admin panel, about page, or configuration files. Check installation directories for version manifest or release notes.Affected if The installed version is below 21.6 (e.g., 21.5, 21.0, older)
-
Confirm web interface is enabledVerify that the Yordam web application is accessible by accessing the system URL in a browser or checking if the web service is running.Affected if The web interface is exposed and accessible to users or attackers
-
Test for reflected input in web pagesSubmit a benign test payload (e.g., a simple text string like 'TESTINPUT') in web form fields or URL parameters and observe if the same value appears unmodified in the page response.Affected if User-supplied input is reflected back in HTML responses without sanitization or encoding
-
Check input validation configurationReview web application configuration files or settings for any input validation, sanitization, or output encoding controls.Affected if No input validation or output encoding is configured for user-supplied data
You are affected if Yordam Library Automation System version is below 21.6 and the web interface is accessible, with user input being reflected without sanitization in page responses.
Generated from the published advisory. Verify against your own configuration.
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 · scoped21.6
Upgrade to version 21.6 or later. Additionally, implement proper input validation and output encoding on all user-supplied data before rendering in HTML.
21.6
- 1. Create a complete backup of the current Library Automation System installation and database
- 2. Verify the current installed version of Yordam Informatics Library Automation System
- 3. Obtain the version 21.6 update package from the official vendor (Yordam Informatics)
- 4. Apply the upgrade to version 21.6 following vendor-provided installation documentation
- 5. Verify the upgrade was successful by checking the new version number
- 6. Test the application functionality to ensure proper operation after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1301 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-1301 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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