CVE-2025-36320: Vulnerabilities found in Watson Data Intelligence
IBM watsonx.data intelligence 5.2.0, 5.2.1, 5.2.2, 5.3.0 is vulnerable to stored cross-site scripting. This vulnerability allows an authenticated user to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.
Security readout for executives and security teams
Plain-English summary
CVE-2025-36320 is a stored cross-site scripting issue in IBM watsonx.data intelligence. An authenticated user could place JavaScript into the web interface, changing trusted UI behavior and potentially exposing credentials during an active session.
Executive priority
Treat this as a moderate-priority application security fix. It is not described as internet-wide critical, but credential exposure inside trusted sessions can create business risk if affected systems hold sensitive data.
Technical view
IBM reports CWE-79 stored XSS affecting watsonx.data intelligence 5.2.0, 5.2.1, 5.2.2, and 5.3.0. The CVSS 3.1 score is 6.4 with low complexity, low privileges required, changed scope, and low confidentiality and integrity impact.
Likely exposure
Exposure is limited to deployments running the listed IBM watsonx.data intelligence versions where authenticated users can access the Web UI.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not listed as CISA KEV. Exploitation requires authenticated access to the application.
Researcher notes
The bundle identifies a vendor advisory tagged as patch, but does not include exact fixed versions or mitigation details. Avoid assuming broader IBM products are affected. Validate exposure by product name, version, and authenticated Web UI reachability.
Mitigation direction
Review IBM advisory 7277801 for fixed versions and patch instructions.
Apply IBM-provided updates or interim fixes for affected deployments.
Restrict Web UI access to trusted authenticated users where possible.
Monitor vendor guidance for any revised affected versions or mitigations.
Validation and detection
Inventory IBM watsonx.data intelligence deployments and record exact versions.
Confirm whether any deployment runs 5.2.0, 5.2.1, 5.2.2, or 5.3.0.
Review application audit logs for suspicious stored content changes.
Verify remediation status against IBM advisory 7277801.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.