Cyber Resilience

CVE-2023-28512

Ibm Watson Cp4D Data Stores 4.6.0 … 4.6.2

Published
03 March 2024
Modified
29 January 2025
Patch / advisory
CVSS Score v3.1 5.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS Score 0.0055 43th percentile
Risk Priority 46 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-28512 is a medium-severity External Control of Assumed-Immutable Web Parameter (CWE-472) vulnerability in Ibm Watson Cp4D Data Stores. Its CVSS base score is 5.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 43th 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 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 Watson CP4D Data Stores 4.6.0, 4.6.1, and 4.6.2 could allow an attacker with specific knowledge about the system to manipulate data due to improper input validation. IBM X-Force ID: 250396.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

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-26282Same product: Ibm Watson Cp4D Data Stores
CVE-2023-27291Same product: Ibm Watson Cp4D Data Stores
CVE-2025-13096Same vendor: Ibm
CVE-2023-35016Same vendor: Ibm
CVE-2025-36324Same vendor: Ibm
CVE-2025-14290Same vendor: Ibm
CVE-2025-36039Same vendor: Ibm
CVE-2026-17069Same vendor: Ibm
CVE-2025-2987Same vendor: Ibm
CVE-2025-36442Same vendor: Ibm

Affected Assets

ibm
watson cp4d data stores
4.6.0, 4.6.1, 4.6.2

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 directly requires validation of all inputs, eliminating the assumption that client-supplied parameters remain immutable.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require server-side validation of all inputs instead of trusting client-supplied immutable parameters.

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

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Secure coding standards require server-side verification of client-supplied data, eliminating the root cause of external control of immutable parameters.

finds

Security testing in development and acceptance will detect parameter tampering vulnerabilities before deployment.

prevents

Secure development lifecycle mandates input validation and integrity checks that directly prevent external tampering of assumed-immutable parameters.

prevents

Application security requirements explicitly call for validation of all inputs, including hidden fields, mitigating CWE-472.

References