CVE-2025-36320: IBM watsonx.data XSS Vulnerability

CVE-2025-36320 Overview

CVE-2025-36320 is a stored Cross-Site Scripting (XSS) vulnerability affecting IBM watsonx.data intelligence versions 5.2.0, 5.2.1, 5.2.2, and 5.3.0. An authenticated user can embed arbitrary JavaScript code into the Web UI. The injected payload persists and executes in the browser of any user who views the affected content within a trusted session. This alters the intended application behavior and can lead to credential disclosure, session token theft, or unauthorized actions performed on behalf of the victim. The flaw is classified under [CWE-79] (Improper Neutralization of Input During Web Page Generation).

Critical Impact
Authenticated attackers can inject persistent JavaScript into the watsonx.data intelligence Web UI, enabling credential theft and session hijacking against other users within a trusted session.

Affected Products

IBM watsonx.data intelligence 5.2.0
IBM watsonx.data intelligence 5.2.1
IBM watsonx.data intelligence 5.2.2
IBM watsonx.data intelligence 5.3.0

Discovery Timeline

2026-06-30 - CVE-2025-36320 published to NVD
2026-07-01 - Last updated in NVD database

Technical Details for CVE-2025-36320

Vulnerability Analysis

The vulnerability resides in the input handling of the IBM watsonx.data intelligence Web UI. User-supplied data is stored server-side and later rendered in the browser without adequate output encoding or sanitization. An authenticated attacker submits a payload containing JavaScript through a UI field that accepts free-form text. When another user loads the page that renders this data, the browser executes the attacker's script in the context of the trusted application origin.

Because the payload is stored, exploitation does not require the victim to click a crafted link. Standard navigation to the affected view is sufficient to trigger execution. The CVSS vector indicates a changed scope, meaning the injected script can affect resources beyond the vulnerable component, such as other browser contexts or downstream services the victim can access.

Root Cause

The root cause is missing or insufficient neutralization of HTML and JavaScript metacharacters in user-controlled fields before they are rendered in the Web UI. The application trusts stored input at render time and emits it into the DOM without contextual output encoding, allowing <script> tags or event handler attributes to be interpreted by the browser.

Attack Vector

An authenticated user with low privileges submits a JavaScript payload through an input field in the watsonx.data intelligence Web UI. The payload is persisted in the application database. When any user, including higher-privileged administrators, views the record, the script executes in their browser. The attacker can then exfiltrate session cookies, read page content, submit authenticated requests, or capture credentials through injected form overlays.

Refer to the IBM Support Document for vendor-specific technical details and remediation guidance.

Detection Methods for CVE-2025-36320

Indicators of Compromise

Web UI fields containing HTML tags such as <script>, <img onerror=>, or <svg onload=> stored in application records.
Outbound HTTP requests from user browsers to unfamiliar domains immediately after loading watsonx.data intelligence pages.
Unexpected session token or credential submission events originating from authenticated user sessions.
Abnormal DOM modifications or injected iframes observed during Web UI rendering.

Detection Strategies

Review server-side application logs for POST or PUT requests to watsonx.data intelligence endpoints containing encoded script fragments or common XSS payload patterns.
Inspect stored records in application data stores for HTML or JavaScript content in fields intended to hold plain text.
Deploy a web application firewall (WAF) rule set that flags requests containing script tags, event handler attributes, and javascript: URIs targeting the Web UI.

Monitoring Recommendations

Enable audit logging for all content-modification actions performed through the Web UI and correlate authoring events with subsequent viewer sessions.
Monitor Content Security Policy (CSP) violation reports if CSP headers are deployed on the application.
Alert on anomalous browser-originated requests to external domains that follow authenticated sessions with watsonx.data intelligence.

How to Mitigate CVE-2025-36320

Immediate Actions Required

Apply the IBM security update referenced in the vendor advisory as soon as it is available for your deployed version.
Audit existing stored content in watsonx.data intelligence for HTML or JavaScript payloads and sanitize or remove suspicious records.
Restrict authoring privileges to trusted users only until patches are applied.
Rotate credentials and invalidate active sessions for any users suspected of viewing malicious content.

Patch Information

IBM has published remediation guidance in the IBM Support Document. Administrators should upgrade IBM watsonx.data intelligence to the fixed release identified in the advisory. Verify that versions 5.2.0, 5.2.1, 5.2.2, and 5.3.0 are updated to the vendor-supplied patched release.

Workarounds

Enforce a strict Content Security Policy that disallows inline scripts and restricts script sources to trusted origins.
Configure a reverse proxy or WAF to filter requests containing script tags or event handler attributes targeting Web UI endpoints.
Limit account creation and role assignments so that only vetted users can submit content to the Web UI until the patch is applied.
Educate administrators to avoid viewing user-submitted content in privileged browser sessions until remediation is complete.

bash

# Example Content Security Policy header to restrict inline script execution
Content-Security-Policy: default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'self'