IBM watsonx.data EUVD-2025-210382

The attacker must hold a valid authenticated account with at least low-level privileges in the IBM watsonx.data intelligence Web UI, as confirmed by PR:L in the CVSS vector - unauthenticated external attackers cannot directly trigger the stored XSS without first obtaining credentials. A stored input field within the Web UI must accept and persist unsanitized user content (the exact field or feature is not specified in the available data and should be clarified via IBM's advisory). Exploitation impact is further bounded to authenticated victim users who actively browse the page containing the injected payload during an active session. The vendor's UI:N metric suggests the payload may execute without requiring explicit victim interaction beyond normal authenticated navigation, but this should be verified given it is atypical for stored XSS.

The CVSS 6.4 Medium rating is derived from a network-accessible, low-complexity attack vector with low privilege requirements and a scope change affecting other users' sessions. One notable discrepancy exists: the vendor-submitted UI:N metric is atypical for stored XSS, which conventionally requires a victim to load the affected page (normally scored UI:R); this should be independently verified against IBM's advisory at https://www.ibm.com/support/pages/node/7277801 to determine whether the payload auto-executes without any page-load action. EPSS data was not provided, and the vulnerability is absent from the CISA KEV catalog, indicating no confirmed widespread active exploitation at time of analysis. No public POC was identified. Real-world risk is moderate-to-elevated for organizations running this platform, because credential disclosure within trusted sessions can enable session hijacking or lateral movement despite the moderate base score - the stored persistence means a single successful injection compounds across all subsequent victim visits.

An authenticated low-privileged user - such as a data analyst with basic platform access - navigates to a stored input field in the watsonx.data intelligence Web UI (for example, a dataset annotation, metadata field, or shared workspace comment) and submits a crafted JavaScript payload. When any other authenticated user subsequently browses to the page rendering that field, the script executes silently in their browser, potentially exfiltrating session cookies, authentication tokens, or credentials to an attacker-controlled endpoint. No public POC has been identified, but the attack technique is a well-documented exploitation pattern for stored XSS in enterprise web applications.