Cross-site scripting in IBM Cognos Analytics
Priority LOW 27CWE-79Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- Cross-site scripting
- Confidentiality · integrity · availability
- Low · Low · None
- Fix status
- No fix listed
Attack profile from CVSS 3.0 · NVD. Fix status from CNA. Impact type from CWE-79.
Summary
IBM Cognos Analytics 11.0 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: 138819.
Why it matters now
EPSS 0.01066 64th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| IBM | Cognos Analytics | 11.0 | — | No fix listed | CNA |
- Cognos Analytics VendorIBM Affected 11.0 Fixed in — No fix listed CNA
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2018-1413
- 2026-10-03 Alias added: GHSA-fm3j-q4jm-x562
References
More IBM Cognos Analytics vulnerabilities
- TI-2020-03885 IBM Cognos Analytics 11.0 and 11.1 DQM API allows submitting of all control requests in… CVSS 3.1CRITICAL 10.0
- TI-2022-18240 IBM Cognos Analytics server-side request forgery CVSS 3.1CRITICAL 9.1
- TI-2021-16384 Unrestricted file upload in IBM Cognos Analytics CVSS 3.1CRITICAL 9.8
- TI-2019-03124 Path traversal in IBM Cognos Analytics CVSS 3.0CRITICAL 9.1
- TI-2024-16521 IBM Cognos Analytics log injection CVSS 3.1HIGH 8.6
- TI-2020-03850 Cross-site scripting in IBM Cognos Analytics CVSS 3.1HIGH 8.8
Sources
- CVE-2018-1413 · CVE Program
- CVE-2018-1413 · NVD
- FIRST EPSS
- GHSA-fm3j-q4jm-x562 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences