Cross-site scripting in IBM Security Guardium Big Data Intelligence
Priority LOW 29CWE-79Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- 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 · CNA. Fix status from CNA. Impact type from CWE-79.
Summary
IBM Security Guardium Big Data Intelligence (SonarG) 3.1 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: 137777.
Why it matters now
EPSS 0.00877 59th 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
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2018-1376
- 2026-10-03 Alias added: GHSA-wpww-xrp2-j2qc
References
More IBM Security Guardium Big Data Intelligence vulnerabilities
- TI-2018-01268 Missing brute-force protection in IBM Security Guardium Big Data Intelligence CVSS 3.0CRITICAL 9.8
- TI-2018-01267 IBM Security Guardium Big Data Intelligence (SonarG) 3.1 does not require that users… CVSS 3.0CRITICAL 9.8
- TI-2019-03226 XML external entity injection in IBM Security Guardium Big Data Intelligence CVSS 3.1HIGH 8.2
- TI-2019-03208 Missing brute-force protection in IBM Security Guardium Big Data Intelligence CVSS 3.1HIGH 7.5
- TI-2018-01270 Session fixation in IBM Security Guardium Big Data Intelligence CVSS 3.0HIGH 7.5
- TI-2019-03224 Resource allocation without limits in IBM Security Guardium Big Data Intelligence CVSS 3.1HIGH 7.5
Sources
- CVE-2018-1376 · CVE Program
- CVE-2018-1376 · NVD
- FIRST EPSS
- GHSA-wpww-xrp2-j2qc · 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