Security Resilience

CVE-2023-38007

XSS in Ibm Cloud Pak System 2.3.3.6 … 2.3.5.0

Published
27 June 2025
Modified
14 August 2025
Patch / advisory
CVSS Score v3.1 5.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
EPSS Score 0.0026 18th percentile
Risk Priority 40 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-38007 is a medium-severity Basic XSS (CWE-80) vulnerability in Ibm Cloud Pak System. Its CVSS base score is 5.4 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Input Capture (T1056); ranked at the 18th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

executed in the victim's Web browser within the security context of the hosting site.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1204 User Execution Execution
An adversary may rely upon specific actions by a user in order to gain execution.
T1491 Defacement Impact
Adversaries may modify visual content available internally or externally to an enterprise network, thus affecting the integrity of the original content.
T1056 Input Capture Collection
Adversaries may use methods of capturing user input to obtain credentials or collect information.
T1056.003 Web Portal Capture Collection
Adversaries may install code on externally facing portals, such as a VPN login page, to capture and transmit credentials of users who attempt to log into the service.
T1189 Drive-by Compromise Initial Access
Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-42015Same vendor: Ibm
CVE-2023-24957Same vendor: Ibm
CVE-2023-43057Same vendor: Ibm
CVE-2023-35905Same vendor: Ibm
CVE-2023-30435Same vendor: Ibm
CVE-2023-22860Same vendor: Ibm
CVE-2023-35024Same vendor: Ibm
CVE-2023-22595Same vendor: Ibm
CVE-2023-28530Same vendor: Ibm
CVE-2023-40684Same vendor: Ibm

Affected Assets

ibm
cloud pak system
2.3.3.6, 2.3.3.7, 2.3.4.0, 2.3.4.1, 2.3.5.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.1.2
  • V1.3.2
  • V1.2.1
  • V1.3.1

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Developer testing and evaluation can discover missing or incorrect neutralization of script tags through targeted XSS test cases.

Input validation explicitly requires checking and neutralizing untrusted web inputs containing script-related characters before they reach a downstream renderer.

Output filtering can catch or sanitize unneutralized script content before it is served to users.

Secure engineering principles include mandatory output encoding and neutralization of HTML metacharacters to stop injection at the source.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly require output encoding and input validation that prevent basic XSS.

PR.PS-02 partial match
blocks

Patching and EOL replacement can remediate known XSS instances in libraries or frameworks (partial) but do nothing to enforce input neutralization in application code (none).

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Security testing in development catches unneutralized script tags before release.

prevents

Training helps some developers learn proper output encoding for script-related tags, but the effect is a minority one: training is fallible, not all developers receive adequate depth on encoding specifics, and A.6.3 is broader awareness rather than the secure-coding practice A.8.28 mandates, so the bulk of XSS instances still arise.

prevents

Secure coding standards require proper escaping of <, >, & to block XSS.

prevents

A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; XSS is a regular software CWE that secure coding (8.28) and security testing (8.29) reach at `partial`, and A.8.30 inherits that ceiling.

finds

A.8.8's reach is disclosure-based (published advisories, component inventory, vulnerability scanning); it finds XSS where the instance carries a CVE in a tracked third-party component or surfaces through its named penetration-testing route, but most XSS lives in first-party custom code that A.8.8 does not read — the same scope seam that graded A.8.8 finds CWE-89 = partial.

References