dbcve.org
Cloud Pak For Business AutomationApplication · Ibm

CVE-2025-36436

MEDIUM · 5.4 CVSS v3.1 Published 2026-02-02
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 25.0.0 through 25.0.0 Interim Fix 002, 24.0.1 through 24.0.1 Interim Fix 005, and 24.0.0 through 24.0.0 Interim Fix 007  is vulnerable to stored 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

Stored cross-site scripting (XSS) vulnerability in IBM Cloud Pak for Business Automation Web UI allows authenticated users to inject arbitrary JavaScript code that persists on the server and executes in browsers of other users viewing the affected content, potentially leading to session hijacking and credential disclosure.

MitigationApply the appropriate IBM interim fix: IF002 for version 25.0.0, IF005 for version 24.0.1, or IF007 for version 24.0.0. Additionally, implement output encoding and input validation on affected UI components.

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:= 24.0.0= 24.0.1= 25.0.0

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 IBM Cloud Pak for Business Automation version
    Run the command to retrieve the installed version of IBM Cloud Pak for Business Automation, typically via the oc get icpa4bcommand or by checking the operator deployment version in your Kubernetes environment.
    Affected if The installed version equals 24.0.0, 24.0.1, or 25.0.0 exactly.
  2. Verify Web UI component is exposed
    Check if the Web UI component is accessible and not disabled. Review the service configuration and ingress/expose settings to confirm the IBM Business Automation Workflow Web UI is reachable.
    Affected if The Web UI is exposed and accessible to authenticated users.
  3. Review user-submitted content storage locations
    Inspect the database or content storage for the Web UI where user-generated content is persisted, such as form submissions, comments, or profile fields. Look for any unexpected script tags or JavaScript payloads.
    Affected if Any stored content contains unsanitized HTML or JavaScript code that could execute in other user browsers.
  4. Check application logs for XSS injection attempts
    Search the application and web server logs for patterns indicative of XSS injection attempts, such as <script>, javascript:, onerror=, onload=, or other HTML event handlers in request parameters.
    Affected if Logs contain repeated XSS injection patterns targeting the Web UI endpoints.

You are affected if your IBM Cloud Pak for Business Automation version is exactly 24.0.0, 24.0.1, or 25.0.0 AND the Web UI 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the appropriate IBM interim fix: IF002 for version 25.0.0, IF005 for version 24.0.1, or IF007 for version 24.0.0. Additionally, implement output encoding and input validation on affected UI components.

Recommended fix Moderate confidence

Apply the appropriate Interim Fix (IF) for your version: 25.0.0-IF002+, 24.0.1-IF005+, or 24.0.0-IF007+

  1. 1. Identify the exact version of IBM Cloud Pak for Business Automation currently installed by checking the CP4BA deployment configuration and version information.
  2. 2. For version 25.0.0: Apply Interim Fix 002 or later (e.g., 25.0.0-IF003 or newer if available).
  3. 3. For version 24.0.1: Apply Interim Fix 005 or later (e.g., 24.0.1-IF006 or newer if available).
  4. 4. For version 24.0.0: Apply Interim Fix 007 or later (e.g., 24.0.0-IF008 or newer if available).
  5. 5. Obtain the interim fix from IBM Fix Central (https://www.ibm.com/support/fixcentral) by searching for the specific CVE or the interim fix number.
  6. 6. Follow IBM's standard process for applying interim fixes to Cloud Pak for Business Automation, which typically involves updating the operator deployment with the new fix package.
  7. 7. After applying the fix, verify the patch was successfully installed by checking the version/fix level in the deployment.
  8. 8. Test the Web UI functionality to confirm the XSS fix does not introduce regressions.
Caveat Interim Fixes are cumulative and typically backward-compatible; apply during a planned maintenance window

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cloud Pak For Business Automation Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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