CVE-2025-36088
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 TS4500 1.11.0.0-D00, 1.11.0.1-C00, 1.11.0.2-C00, and 1.10.00-F00 web GUI is vulnerable to cross-site scripting. This vulnerability allows an authenticated user 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 confidenceIBM TS4500 tape library web GUI versions prior to 1.11.0.2-C00 and 1.10.00-F00 contains a stored cross-site scripting vulnerability allowing authenticated users to inject arbitrary JavaScript code through the Web UI, potentially enabling credentials theft within trusted sessions.
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.10.00-f00= 1.11.0.0-d00= 1.11.0.1-c00= 1.11.0.2-c00= 2.11.0.0-b00= 2.11.0.1-c00= 2.11.0.2-b00= 2.11.0.4-c00CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check TS4500 firmware version via web GUILog into the TS4500 web interface and navigate to Settings > System > Library Information. Locate the Firmware Version field.Affected if The firmware version displayed is 1.10.00-f00, 1.11.0.0-d00, 1.11.0.1-c00, or 1.11.0.2-c00 (or any version prior to 1.11.0.2-C00 or 1.10.00-F00).
-
Check Diamondback tape library firmware versionLog into the Diamondback web GUI and navigate to the System Information or Library Status page to view the firmware version.Affected if The firmware version displayed is 2.11.0.0-b00, 2.11.0.1-c00, 2.11.0.2-b00, or 2.11.0.4-c00.
-
Verify web GUI is enabledAccess the web interface by entering the device IP in a browser. Confirm the login page loads successfully.Affected if The web GUI is accessible and accepts authentication credentials.
-
Check for user input fields in web GUIAfter logging in, inspect web forms such as user profile settings, device naming, or configuration input fields where authenticated users can enter custom text.Affected if There are input fields that accept user-supplied text and display it back in the interface without visible sanitization indicators.
Your environment is affected if the web GUI is enabled and the installed firmware version matches one of the vulnerable versions listed in the CVE.
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 dataApply IBM's available patches or firmware updates for the TS4500 web GUI to implement proper input validation and output encoding; validate all user-supplied input in web interfaces.
- Consultation4.0 h
- Implementation3.0 h
- Testing3.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 $3,440.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36088 — 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-36088 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