CVE-2023-28512
Ibm Watson Cp4D Data Stores 4.6.0 … 4.6.2
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:NCVSS 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-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 Data Manipulation (T1565); ranked at the 47th 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
- 🇪🇺 ENISA EUVD: EUVD-2023-32182
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
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
SI-10 directly requires validation of all inputs, eliminating the assumption that client-supplied parameters remain immutable.
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.
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)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
Security testing in development and acceptance will detect parameter tampering vulnerabilities before deployment.
Training developers that hidden fields, cookies and URL parameters are externally controllable addresses the knowledge gap behind CWE-472, but it is a fallible human practice that catches a minority of instances, consistent with the A.6.3 -> CWE-598 anchor.
Secure coding standards require server-side verification of client-supplied data, eliminating the root cause of external control of immutable parameters.
A.8.30 carries its effect through the secure-design, coding and testing practices (8.25–8.29) its contract requires of the supplier, so a well-implemented clause reduces ordinary input-validation defects like trusting hidden form fields in delivered code the way those practices do; the owner has ruled A.8.30's ceiling on `prevents` at `partial`, and the remainder is the fallibility of the contracted practice plus code the supplier did not write.
A.8.8's reach is disclosure-based (vulnerability scanning, vendor advisories, third-party component tracking) plus limited penetration testing. CWE-472 is a first-party web application implementation flaw; A.8.8 finds it where it has been published as a CVE (and there are many) or where a pen test happens to exercise the relevant hidden fields, but the bulk of instances in custom code never surface as advisories and are outside A.8.8's reach.