dbcve.org
Cloud Pak SystemApplication · Ibm

CVE-2023-38007

MEDIUM · 5.4 CVSS v3.1 Published 2025-06-27
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 System 2.3.5.0, 2.3.3.7, 2.3.3.7 iFix1 on Power and 2.3.3.6, 2.3.3.6 iFix1, 2.3.3.6 iFix2, 2.3.4.0, 2.3.4.1 on Intel operating systems is vulnerable to HTML injection. A remote attacker could inject malicious HTML code, which when viewed, would be executed in the victim's Web browser within the security context of the hosting site.

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 Cloud Pak System versions 2.3.3.6 through 2.3.5.0 contain an HTML injection vulnerability where unsanitized user-supplied input is rendered in web pages without proper encoding. An unauthenticated remote attacker can embed malicious HTML/JavaScript into affected fields, which executes in the victim's browser within the security context of the hosting site, potentially leading to session hijacking or credential theft.

MitigationApply IBM Cloud Pak System security patches for version 2.3.3.7+ (Power) and 2.3.4.2+ (Intel), or upgrade to a patched release. Additionally, implement input validation and output encoding on all user-facing fields to prevent HTML injection.

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 SystemApplication
Affected:= 2.3.3.6= 2.3.3.7= 2.3.4.0= 2.3.4.1= 2.3.5.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 IBM Cloud Pak System version
    Locate the installed version of IBM Cloud Pak System in the system documentation, administration console, or by running the platform version command provided by IBM (typically via `cpctl version` or through the Cloud Pak console).
    Affected if The installed version is 2.3.3.6, 2.3.3.7, 2.3.4.0, 2.3.4.1, or 2.3.5.0.
  2. Confirm version is within affected range
    Compare your installed version against the affected range: versions 2.3.3.6 through 2.3.5.0 (inclusive).
    Affected if Your version falls within 2.3.3.6 to 2.3.5.0.
  3. Identify accessible web interfaces
    Locate any web-based login or user input fields in the IBM Cloud Pak System administration console or user portals that accept user-supplied data.
    Affected if Web interfaces are exposed and accept user input without confirmation that output encoding is applied.
  4. Review user input handling
    Examine the application's response when submitting HTML or script tags in web form fields (login forms, search fields, profile fields). Observe whether the input is reflected back in the response without sanitization.
    Affected if User-supplied input is rendered in web pages without proper HTML encoding.

You are affected if IBM Cloud Pak System version 2.3.3.6 through 2.3.5.0 is installed and web interfaces render unsanitized user input.

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 IBM Cloud Pak System security patches for version 2.3.3.7+ (Power) and 2.3.4.2+ (Intel), or upgrade to a patched release. Additionally, implement input validation and output encoding on all user-facing fields to prevent HTML injection.

Recommended fix Moderate confidence

IBM Cloud Pak System 2.3.5.0 or later (contact IBM for exact fixed release)

  1. 1. Back up all critical data and configurations before initiating the upgrade
  2. 2. Review IBM Cloud Pak System upgrade documentation for your current version
  3. 3. Plan maintenance window as upgrade may require downtime
  4. 4. Upgrade IBM Cloud Pak System to version 2.3.5.0 or later fixed release
  5. 5. After upgrade, verify the HTML injection vulnerability is resolved by testing input validation in affected web interfaces
  6. 6. Monitor IBM Cloud Pak System for any post-upgrade issues
Caveat Review IBM upgrade documentation for potential compatibility changes and ensure applications are tested against new version before production deployment

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

Fix this in Cloud Pak System 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 help mitigating

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-38007 — 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-38007 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