dbcve.org
Watsonx.data IntelligenceApplication · Ibm

CVE-2025-36323

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

IBM watsonx.data intelligence versions 5.2.0 through 5.3.0 contain a stored cross-site scripting (XSS) vulnerability in the Web UI. An authenticated attacker can inject malicious JavaScript code into UI fields that persists and executes in the browsers of other users viewing the affected content, potentially exposing credentials or session data within a trusted session.

MitigationImplement proper input validation and output encoding for all user-supplied data in the Web UI; apply Content Security Policy (CSP) headers to mitigate XSS execution. Until an official patch is released, consider restricting administrative UI access and monitoring for suspicious input patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Watsonx.data IntelligenceApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed version
    Access the IBM watsonx.data intelligence administrative console or use the version command/utility provided by the installation. Determine the exact version number running in your environment.
    Affected if The installed version is 5.2.0, 5.3.0, or any version in between these two releases (e.g., 5.2.1, 5.2.2, 5.2.3, 5.2.4, 5.2.5). Note: All versions within this range are affected.
  2. Confirm Web UI is accessible
    Verify that the Web UI component is enabled and network-accessible. Check the service configuration or attempt to reach the Web UI login endpoint via browser or HTTP tool.
    Affected if The Web UI is enabled and accessible. The vulnerability exists specifically within the Web UI component, so this must be active for exploitation to occur.
  3. Review access logs for XSS injection attempts
    Examine IBM watsonx.data intelligence server logs, Web UI access logs, or HTTP request logs for patterns indicative of XSS payloads. Look for common XSS signatures such as <script>, javascript:, onerror=, onload=, or other HTML/script tags in user input fields.
    Affected if Logs contain requests with suspicious script tags or JavaScript event handlers submitted through UI input fields, indicating exploitation attempts.
  4. Inspect stored UI field content
    Review stored configurations, user profiles, metadata fields, or any database tables that hold data displayed in the Web UI. Examine fields where multiple users can input or view content (such as descriptions, names, comments, or metadata).
    Affected if Stored content in UI fields contains unexpected script tags, encoded JavaScript, or suspicious HTML that was not intentionally entered by the current user.
  5. Monitor for anomalous user sessions
    Review active sessions and recent authentication events in the administrative console or audit logs. Look for sessions originating from unexpected IP addresses or sessions exhibiting unusual behavior.
    Affected if Multiple users report that their sessions behave unexpectedly, or audit logs show actions performed under their accounts that they did not initiate (potential credential/session theft via XSS).

Your environment is affected if the installed IBM watsonx.data intelligence version falls between 5.2.0 and 5.3.0 inclusive AND the Web UI component is enabled and accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding for all user-supplied data in the Web UI; apply Content Security Policy (CSP) headers to mitigate XSS execution. Until an official patch is released, consider restricting administrative UI access and monitoring for suspicious input patterns.

Fix this in Watsonx.data Intelligence Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-36323 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-36323 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data