dbcve.org
Cloud Pak For Business AutomationApplication · Ibm

CVE-2024-52365

MEDIUM · 5.4 CVSS v3.1 Published 2025-02-05
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

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 Cloud Pak for Business Automation 18.0.0, 18.0.1, 18.0.2, 19.0.1, 19.0.2, 19.0.3, 20.0.1, 20.0.2, 20.0.3, 21.0.1, 21.0.2, 21.0.3, 22.0.1, and 22.0.2 is vulnerable to stored cross-site scripting. This vulnerability allows authenticated users 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

This is a stored cross-site scripting (XSS) vulnerability in IBM Cloud Pak for Business Automation's Web UI. Authenticated users can inject malicious JavaScript code into the Web UI that gets persistently stored and executed in the browsers of other users who view the affected interface, potentially allowing session hijacking or credential theft within a trusted session.

MitigationApply IBM's security patch for this vulnerability to the affected versions (18.0.0-22.0.2). Until patched, implement strict input validation and output encoding on user-supplied content displayed in the Web UI, and consider deploying Content Security Policy (CSP) headers to mitigate XSS execution.

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
Cloud Pak For Business AutomationApplication
Affected:= 18.0.0= 18.0.1= 18.0.2= 19.0.1= 19.0.2= 19.0.3= 20.0.1= 20.0.2= 20.0.3= 21.0.1= 21.0.2= 21.0.3

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. Verify IBM Cloud Pak for Business Automation is installed
    Locate the installation directory or check for running containers associated with IBM Cloud Pak for Business Automation. Use your organization's standard method for listing installed IBM software.
    Affected if The product is installed and running.
  2. Check the installed version number
    Use IBM's version retrieval command or check the product's About/Version information in the administration console. Compare your version to the affected list: 18.0.0, 18.0.1, 18.0.2, 19.0.1, 19.0.2, 19.0.3, 20.0.1, 20.0.2, 20.0.3, 21.0.1, 21.0.2, 21.0.3.
    Affected if Your installed version matches one of these exact versions.
  3. Confirm the Web UI component is enabled
    Access the administration or configuration settings for Cloud Pak for Business Automation and verify whether the Web UI interface is enabled and accessible.
    Affected if The Web UI is enabled and reachable over the network.
  4. Identify users with access to the Web UI
    Review the user accounts and roles configured in IBM Cloud Pak for Business Automation that have permission to access the Web UI and create or view content.
    Affected if Multiple user accounts exist with Web UI access, allowing the stored XSS to affect other users viewing injected content.

You are affected if IBM Cloud Pak for Business Automation is installed with a version matching 18.0.0 through 21.0.3, the Web UI is enabled, and multiple users have access to view content in that interface.

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

Apply IBM's security patch for this vulnerability to the affected versions (18.0.0-22.0.2). Until patched, implement strict input validation and output encoding on user-supplied content displayed in the Web UI, and consider deploying Content Security Policy (CSP) headers to mitigate XSS execution.

Fix this in Cloud Pak For Business Automation Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-52365 — 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-2024-52365 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