CVE-2025-2895
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 · uneditedIBM Cloud Pak System 2.3.3.6, 2.3.36 iFix1, 2.3.3.7, 2.3.3.7 iFix1, 2.3.4.0, 2.3.4.1, and 2.3.4.1 iFix1 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 · high confidenceIBM Cloud Pak System contains an HTML injection vulnerability in its web interface. A remote attacker can inject malicious HTML code through user-controlled input that gets rendered in victims' browsers without proper sanitization. While this is less severe than XSS (no direct JavaScript execution), it allows attackers to spoof content, conduct phishing attacks, and potentially escalate to script injection in certain contexts.
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= 2.3.3.6= 2.3.3.7= 2.3.4.0= 2.3.4.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed IBM Cloud Pak System versionAccess the system administration console or use the 'cpctl status' command-line tool to retrieve the current platform version. Alternatively, check the /opt/icpfs directory or the system's package management files for the installed version number.Affected if The installed version matches exactly 2.3.3.6, 2.3.3.7, 2.3.4.0, or 2.3.4.1
-
Confirm web interface is enabled and accessibleVerify that the IBM Cloud Pak System web console (typically accessible via HTTPS on port 9443 or similar) is running and reachable. Check the service status using 'kubectl get pods -n ibm-system' or the equivalent container orchestration command.Affected if The web interface service is running and externally or internally accessible without additional authentication barriers
-
Identify user-controlled input fields in the web interfaceLog into the Cloud Pak System web console and navigate to user-facing forms such as user profile settings, search fields, configuration panels, or any input that accepts and displays user-supplied text back to the browser.Affected if The interface contains input fields that accept user data and render it back in HTML responses without visible sanitization indicators
-
Test for HTML injection vulnerabilityUsing an authenticated session in the web interface, submit simple HTML tags such as '<b>test</b>', '<i>test</i>', or '<img src=x onerror=alert(1)>' into identified input fields, then view the rendered output to see if the tags are executed as HTML.Affected if Submitted HTML tags are rendered as bold, italic, or other HTML elements rather than displayed as plain text
A user is affected if their IBM Cloud Pak System version matches 2.3.3.6, 2.3.3.7, 2.3.4.0, or 2.3.4.1 AND the web interface is accessible with input fields that render unescaped HTML.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply IBM's vendor patch for this vulnerability when available. Until then, implement input validation and output encoding at intermediate network layers (WAF) to filter malicious HTML tags and attributes.
Latest available IBM Cloud Pak System version beyond 2.3.4.1 iFix1 (refer to IBM security bulletin for exact fixed release)
- Check the current IBM Cloud Pak System version by navigating to the system administration console
- Access the IBM Cloud Pak System support portal or IBM Fix Central to identify the latest available version beyond 2.3.4.1 iFix1
- Review the IBM security bulletin for CVE-2025-2895 to confirm the specific fixed release version
- Plan an upgrade window following IBM Cloud Pak System upgrade procedures
- Back up the current system configuration and data
- Perform the upgrade to the fixed version following IBM's documented upgrade process
- Verify the upgrade was successful and the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2895 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-2895 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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