CVE-2025-36239
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 · uneditedIBM Storage TS4500 Library 1.11.0.0 and 2.11.0.0 is vulnerable to cross-site scripting. This vulnerability allows an unauthenticated attacker to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.
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 confidenceThis is a stored (persistent) cross-site scripting (XSS) vulnerability in the IBM Storage TS4500 Library Web UI affecting versions 1.11.0.0 and 2.11.0.0. An unauthenticated attacker can inject arbitrary JavaScript code into the web interface, which executes in the browsers of authenticated users viewing the compromised content, potentially allowing credential or session token theft.
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= 1.11.0.0= 2.11.0.0= 1.11.0.0= 2.11.0.0CVSS 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 the firmware versionLog into the TS4500 or Diamondback tape library management interface and navigate to System > Overview or use the CLI command to display firmware version (typically 'show version' or accessible via the web dashboard)Affected if The displayed firmware version is exactly 1.11.0.0 or 2.11.0.0
-
Confirm the product modelVerify whether the device is an IBM Storage TS4500 Library or IBM Diamondback Tape Library by checking the system information page in the Web UI or hardware labelAffected if The device is either model and the version matches step 1
-
Verify Web UI is exposedCheck if the Web UI service (HTTP/HTTPS on the management port) is accessible by attempting to reach the management IP in a browser or via curl/curl equivalentAffected if The Web UI responds and is reachable from the network being checked
-
Inspect stored data for injected scriptsReview user-editable fields in the Web UI (such as device naming, user comments, or configuration fields) and check the page source for any <script> tags, event handlers (onmouseover, onerror, onclick), or javascript: URIs that were not intentionally addedAffected if Unexpected script tags or event handlers are present in any stored configuration field
A system is affected if it runs IBM Storage TS4500 or Diamondback firmware version 1.11.0.0 or 2.11.0.0 with the Web UI enabled, and malicious script content is found injected into stored Web UI fields.
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.
From vendor dataImplement input validation and proper output encoding for all user-supplied data in the Web UI; deploy Content Security Policy (CSP) headers to mitigate XSS execution; contact IBM for available patches or hotfixes.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36239 — 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-36239 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