CVE-2019-4115
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 WebSphere eXtreme Scale 8.6 Admin API is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 158113.
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 WebSphere eXtreme Scale 8.6 Admin API contains a stored cross-site scripting (XSS) vulnerability in its web interface. Attackers can inject malicious JavaScript code through the Admin API that executes in the browsers of authenticated administrators, potentially enabling session hijacking and credential 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>= 8.6.0, < 8.6.1.3CVSS 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.
-
Identify installed versionRun the appropriate version detection command or check the product installation directory for the IBM WebSphere eXtreme Scale version information. Common methods include checking the installation logs, using the version command if available, or inspecting the product manifest files.Affected if The installed version is 8.6.0, 8.6.0.0.1, 8.6.0.0.2, 8.6.0.0.3, 8.6.0.0.4, 8.6.0.0.5, 8.6.0.0.6, 8.6.1, 8.6.1.0.1, or 8.6.1.0.2 (any version >= 8.6.0 but < 8.6.1.3).
-
Confirm Admin API is enabledLocate and inspect the configuration files or deployment settings that control the IBM WebSphere eXtreme Scale Admin API service. Verify whether the web-based Admin API interface is currently enabled and accessible.Affected if The Admin API web interface is enabled and accessible, as the XSS vulnerability specifically affects this component.
-
Review admin API logs for suspicious inputAccess the logs generated by the Admin API, looking for entries that contain unexpected script tags, JavaScript function calls, or other patterns indicative of injected script content in API parameters or administrative inputs.Affected if Log review reveals script injection attempts or unexpected JavaScript content submitted through Admin API endpoints.
You are affected if your installed IBM WebSphere eXtreme Scale version falls within 8.6.0 through 8.6.1.2 and the Admin API web interface is enabled.
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 data8.6.1.3
Apply the IBM security patch for CVE-2019-4115. If immediate patching is unavailable, implement output encoding and input validation on Admin API endpoints, deploy Content Security Policy (CSP) headers, and consider disabling the web UI if not required for operations.
- 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-2019-4115 — 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-2019-4115 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