CVE-2019-4426
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 · uneditedThe Case Builder component shipped with 18.0.0.1 through 19.0.0.2 and IBM Case Manager 5.1.1 through 5.3 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: 162772.
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 · high confidenceIBM Case Manager Case Builder component versions 18.0.0.1-19.0.0.2 and 5.1.1-5.3 contains a stored cross-site scripting (XSS) vulnerability in its Web UI. Attackers can embed malicious JavaScript code that executes in the context of other users' sessions, potentially exfiltrating credentials or session tokens within a trusted session.
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>= 19.0.0.0, <= 19.0.0.3= 18.0.0.0>= 5.3.0, < 5.3.2= 5.1.1= 5.2.0= 5.2.1CVSS 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 IBM Case Manager versionCheck the version of IBM Case Manager installed. In the Case Manager administration console, navigate to the 'About' or 'System Information' section, or inspect the installed files for the version number (typically in the installation directory or configuration files).Affected if The installed version is 5.1.1, 5.2.0, 5.2.1, or between 5.3.0 and 5.3.1 (inclusive).
-
Identify installed IBM Business Automation Workflow versionCheck the version of IBM Business Automation Workflow if deployed. Access the administration console or check installation metadata for the version number.Affected if The installed version is 18.0.0.0, or between 19.0.0.0 and 19.0.0.3 (inclusive).
-
Confirm Case Builder Web UI is accessibleVerify that the Case Builder component is deployed and accessible. Attempt to access the Case Builder login page (typically at /CaseBuilder or /navigator?desktop=casebuilder under the web application context).Affected if Case Builder Web UI is exposed and users can log in to create or edit case types.
-
Review web access logs for XSS payloadsExamine web server or application logs (such as HTTP server logs, IBM HTTP Server logs, or WebSphere Application Server logs) for suspicious patterns in Case Builder input fields. Look for script tags, javascript: URIs, or event handler attributes in query parameters or form submissions.Affected if Logs contain XSS attack patterns (such as <script>, javascript:, onerror=, onload=) submitted to Case Builder endpoints.
-
Inspect stored case data for malicious scriptsIf you have database access, query the Case Manager content repository or solution metadata tables for stored values containing script tags or JavaScript code that may have been injected through Case Builder forms.Affected if Stored case metadata or solution definitions contain embedded script tags or event handler attributes.
You are affected if your IBM Case Manager version is 5.1.1, 5.2.0, 5.2.1, or 5.3.0-5.3.1, OR your IBM Business Automation Workflow version is 18.0.0.0 or 19.0.0.0-19.0.0.3, AND the Case Builder Web UI is accessible to users.
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 data5.3.2
Apply the IBM fix pack for this vulnerability (contact IBM for patch PH12138). Until patched, implement WAF rules to detect and block XSS payloads in Case Builder inputs, and educate users about not clicking suspicious links.
- Consultation3.0 h
- Implementation8.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-4426 — 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-4426 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