CVE-2017-1604
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 Maximo Anywhere 7.5 and 7.6 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: 132851.
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 Maximo Anywhere 7.5 and 7.6 contains a stored cross-site scripting (XSS) vulnerability in the Web UI. Attackers can embed malicious JavaScript code that executes within authenticated users' sessions, potentially enabling credential theft or session hijacking through the trusted session context.
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= 7.5.1.2= 7.5.2.0= 7.5.2.1= 7.5.2.2= 7.6.0.0= 7.6.1.0= 7.6.2.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.
-
Identify Maximo Anywhere versionCheck the installed version by examining the installation directory or checking the build manifest. Look for version files in the installation path or use the Maximo Anywhere administration console to view version information.Affected if The installed version matches 7.5.1.2, 7.5.2.0, 7.5.2.1, 7.5.2.2, 7.6.0.0, 7.6.1.0, or 7.6.2.0
-
Verify Web UI is accessibleConfirm the Maximo Anywhere Web UI is deployed and accessible to users. Check the application server configuration and verify the web application is running.Affected if The Web UI component is enabled and reachable
-
Review user input fields in Web UIInspect the Web UI for input fields that accept user-supplied content, such as description fields, notes, or custom attributes. Examine the application's database or logs for any stored content containing script tags or javascript: URIs.Affected if User-supplied content in Web UI fields is not properly sanitized and contains unsanitized HTML or script tags
-
Check for anomalous scripts in session dataAnalyze recent Web UI sessions and user-generated content for patterns indicating XSS payloads, such as <script> tags, event handlers (onclick, onerror), or javascript: pseudo-protocol URLs in data fields.Affected if Malicious JavaScript code is present in any user-created records visible in the Web UI
You are affected if you are running any of the listed versions (7.5.1.2 through 7.6.2.0) and the Web UI is enabled, with unsanitized user-supplied content present in the application.
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 security patches for this vulnerability, implement robust input validation and output encoding for user-supplied content in the Web UI, and consider Content Security Policy (CSP) headers to mitigate XSS execution.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1604 — 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-1604 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