dbcve.org
Cloud Pak For SecurityApplication · Ibm

CVE-2023-47731

MEDIUM · 5.4 CVSS v3.1 Published 2024-04-23
Fix available
A fix is available. Upgrade to after 1.10.19.0 or later.
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 QRadar Suite Software 1.10.12.0 through 1.10.19.0 and IBM Cloud Pak for Security 1.10.0.0 through 1.10.11.0 is vulnerable to stored cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 272203.

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 · high confidence

A stored cross-site scripting vulnerability in IBM QRadar Suite Software (versions 1.10.12.0-1.10.19.0) and IBM Cloud Pak for Security (versions 1.10.0.0-1.10.11.0) allows authenticated users to embed arbitrary JavaScript code into the Web UI. This malicious script is stored and executed when other users interact with the affected interface, potentially enabling session hijacking and credentials disclosure within trusted sessions.

MitigationApply IBM's vendor-supplied security patches or upgrade to a fixed version (QRadar Suite Software >1.10.19.0, Cloud Pak for Security >1.10.11.0) as specified in IBM Security Bulletin. Implement input validation and output encoding as compensating controls until patching is complete.

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 SecurityApplication
Affected:>= 1.10.0.0, <= 1.10.11.0
Qradar SuiteApplication
Affected:>= 1.10.12.0, <= 1.10.19.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 the installed IBM product
    Determine whether your environment is running IBM QRadar Suite Software or IBM Cloud Pak for Security. Check the product name in your IBM licensing, deployment manifests, or admin console.
    Affected if The product is IBM QRadar Suite Software or IBM Cloud Pak for Security.
  2. Determine the installed version of QRadar Suite
    If using QRadar Suite, run the command to check the version (typically via the admin console or version check utility). Look for a version in the range 1.10.12.0 to 1.10.19.0.
    Affected if The installed version is >= 1.10.12.0 and <= 1.10.19.0.
  3. Determine the installed version of Cloud Pak for Security
    If using Cloud Pak for Security, check the version via the IBM Cloud Pak console or oc commands (oc get cm ibm-cp-security -o yaml). Look for a version in the range 1.10.0.0 to 1.10.11.0.
    Affected if The installed version is >= 1.10.0.0 and <= 1.10.11.0.
  4. Verify Web UI access is enabled
    Confirm that the IBM QRadar or Cloud Pak for Security Web UI interface is accessible and enabled for users. Check admin settings or network configuration for port 443/HTTPS access to the console.
    Affected if The Web UI is enabled and accessible to authenticated users.
  5. Review Web UI input fields for suspicious content
    Inspect stored user-generated content in the Web UI (such as user profiles, dashboards, custom views, or configuration fields) for any unexpected script tags or JavaScript code that may have been injected by an authenticated user.
    Affected if Unexpected script tags or JavaScript code are found stored in Web UI fields.

Your environment is affected if you are running IBM QRadar Suite Software version 1.10.12.0-1.10.19.0 or IBM Cloud Pak for Security version 1.10.0.0-1.10.11.0 with the Web UI 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
Upgrade available Upgrade to a release after 1.10.19.0
Interim mitigation

Apply IBM's vendor-supplied security patches or upgrade to a fixed version (QRadar Suite Software >1.10.19.0, Cloud Pak for Security >1.10.11.0) as specified in IBM Security Bulletin. Implement input validation and output encoding as compensating controls until patching is complete.

Recommended fix Moderate confidence

Cloud Pak for Security: upgrade to 1.10.12.0 or later; QRadar Suite: upgrade to 1.10.19.1 or later

  1. 1. Identify which IBM product is in use: Cloud Pak for Security or QRadar Suite
  2. 2. For Cloud Pak for Security: Plan upgrade from current 1.10.x version to version 1.10.12.0 or later
  3. 3. For QRadar Suite: Plan upgrade from current 1.10.x version to version 1.10.19.1 or later
  4. 4. Review IBM Cloud Pak for Security and QRadar Suite upgrade documentation
  5. 5. Back up all critical data and configurations before upgrading
  6. 6. Schedule maintenance window to perform the upgrade
  7. 7. Execute upgrade to the appropriate fixed version
  8. 8. After upgrade, verify the XSS vulnerability is resolved by testing the Web UI functionality
Caveat Standard upgrade risks apply - review IBM compatibility notes for your specific configuration and ensure all dependent systems are compatible with the target version

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

Fix this in Cloud Pak For Security Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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