CVE-2017-1425
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 Business Process Manager 8.0.1.1 and 8.5.7 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: 127478.
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 Business Process Manager versions 8.0.1.1 and 8.5.7 contain a stored cross-site scripting (XSS) vulnerability in the Web UI. Attackers can embed arbitrary JavaScript code that executes within trusted user sessions, potentially leading to credential disclosure or session hijacking.
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.0.1.1= 8.5.7.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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/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.
-
Verify IBM Business Process Manager versionLocate and inspect the version file or use the BPMVersion command-line tool typically found in the installation directory (for example, look for a versionInfo file or run the version command provided by IBM BPM). Compare the installed version number against the affected versions 8.0.1.1 and 8.5.7.0.Affected if The installed version is exactly 8.0.1.1 or exactly 8.5.7.0
-
Confirm Web UI component is enabledIdentify whether the Web UI component is accessible on your IBM BPM environment. Check application server configurations (such as WebSphere) to confirm the BPM Web UI applications are started and exposed.Affected if The Web UI is enabled and accessible to users
-
Inspect Web UI input fields for stored XSS payloadsIf you have access to the Web UI, examine user input fields (such as process instance names, descriptions, or custom fields) where data can be submitted and stored. Review the underlying database or content store for any entries containing script tags, javascript: URIs, or other XSS patterns.Affected if Stored XSS payloads exist in Web UI input fields or stored content
-
Review server logs for XSS attack indicatorsExamine IBM BPM server logs (such as SystemOut.log or trace files) for suspicious patterns including script tags, event handlers, or encoded XSS vectors submitted through Web UI forms.Affected if Logs contain evidence of XSS payloads being submitted through the Web UI
You are affected if your installed IBM Business Process Manager version is exactly 8.0.1.1 or exactly 8.5.7.0 AND the Web UI component is enabled and accessible in your environment.
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 security patch for this vulnerability (contact IBM support for fix availability). Implement output encoding and input validation as compensating controls until the patch can be applied.
- 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-2017-1425 — 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-2017-1425 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