CVE-2025-36323: 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 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
IBM watsonx.data intelligence has an authenticated cross-site scripting issue in its Web UI. A logged-in user could place JavaScript that runs in another trusted session, potentially exposing credentials or changing what the interface does. The public sources rate this as medium severity, not a confirmed mass-exploitation event.
Executive priority
Treat this as a near-term remediation item, not an emergency absent exploitation evidence. It can affect trusted sessions and credentials, so prioritize systems with broad internal access or sensitive data workflows.
Technical view
CVE-2025-36323 is CWE-79 affecting IBM watsonx.data intelligence 5.2.0, 5.2.1, 5.2.2, and 5.3.0. CVSS 3.1 is 5.4 with network access, low complexity, low privileges, required user interaction, changed scope, and low confidentiality and integrity impact. Availability impact is not indicated.
Likely exposure
Organizations running the listed IBM watsonx.data intelligence versions with user-accessible Web UI are the likely exposure group. Risk is higher where many authenticated users, contractors, or federated identities can access the interface.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not listed as KEV. Exploitation requires authenticated access and user interaction, which reduces broad opportunistic risk but still matters inside trusted enterprise sessions.
Researcher notes
Evidence is limited to the CVE record and IBM advisory reference. Do not assume affected versions beyond those named. The source bundle names a vendor patch reference but does not provide fixed-version detail here, so validation should follow IBM’s advisory.
Mitigation direction
Check IBM advisory for the vendor-supported patch or upgrade path.
Prioritize remediation for affected 5.2.x and 5.3.0 deployments.
Restrict Web UI access to trusted users until remediated.
Review session and credential exposure monitoring for suspicious UI activity.
Avoid adding unsupported filters or code changes without IBM guidance.
Validation and detection
Inventory IBM watsonx.data intelligence versions across environments.
Confirm whether any deployment runs 5.2.0, 5.2.1, 5.2.2, or 5.3.0.
Verify Web UI access paths and authenticated user populations.
Check whether IBM’s advised fix or mitigation is applied.
Review logs for unusual authenticated UI changes or credential-related alerts.
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.