VulnerabilityPublished 30 Jun 2025Updated 24 Aug 2025

CVE-2025-2895: IBM Cloud Pak System · Basic XSS

Affects IBM Cloud Pak SystemSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
IBM Cloud Pak System	Affected 2.3.3.6 – 2.3.4.1 4 affected builds	Fixed in–

AI-suggested

European organizations should implement the following specific mitigation steps: 1) Immediately review and restrict user privileges within IBM Cloud Pak System to the minimum necessary, reducing the number of users who can inject or view potentially malicious content. 2) Implement strict input validation and output encoding on all user-supplied data within the Cloud Pak System interface, if customization or extensions are used, to prevent injection of malicious HTML or scripts. 3) Monitor user activity and logs for unusual behavior indicative of attempted XSS exploitation, such as unexpected script execution or anomalous requests. 4) Educate users about the risks of interacting with untrusted content within the Cloud Pak System interface and encourage cautious behavior when clicking links or opening embedded content. 5) Stay in close contact with IBM for official patches or security advisories and plan for rapid deployment of fixes once available. 6) Consider deploying web application firewalls (WAFs) with rules tailored to detect and block XSS payloads targeting the Cloud Pak System’s web interface. 7) Conduct regular security assessments and penetration testing focused on the Cloud Pak System environment to identify and remediate any residual injection points. These targeted measures go beyond generic advice by focusing on user privilege management, monitoring, and proactive defense tailored to the affected product and vulnerability type.

Description

IBM 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.

Impact

For European organizations using IBM Cloud Pak System, this vulnerability could lead to unauthorized disclosure of sensitive information or manipulation of data through the execution of malicious scripts in users’ browsers. Since IBM Cloud Pak System is used for hybrid cloud management and orchestration, exploitation could allow attackers to perform actions on behalf of legitimate users, potentially leading to privilege escalation or lateral movement within the cloud infrastructure. The impact is particularly significant for organizations handling sensitive or regulated data, such as financial institutions, healthcare providers, and government agencies, where confidentiality and data integrity are paramount. The requirement for user interaction and authentication reduces the risk somewhat but does not eliminate it, especially in large organizations with many users and complex access patterns. Additionally, the scope change in the CVSS vector suggests that the vulnerability could affect multiple components or services within the Cloud Pak System environment, increasing the potential attack surface. Given the widespread adoption of IBM Cloud Pak System across Europe in sectors emphasizing digital transformation and cloud adoption, the vulnerability could disrupt business operations and erode trust if exploited.

CWE-80Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) (opens in a new tab)
Variant weaknessLikelihood of exploit: HighOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages.
Implementation
Carefully check each input parameter against a rigorous positive specification (allowlist) defining the specific characters and format allowed. All input should be neutralized, not just parameters that the user is supposed to specify, but all data in the request, including hidden fields, cookies, headers, the URL…
Implementation · Output Encoding
Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8.
Implementation
With Struts, write all data from form beans with the bean's filter attribute set to true.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
V5.3.3 (opens in a new tab)
Attack patterns
XSS Targeting Non-Script Elements (opens in a new tab)
PHP Remote File Inclusion (opens in a new tab)
XSS Through HTTP Query Strings (opens in a new tab)
XSS Through HTTP Headers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

ibm.com/support/pages/node/7237164 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Aug 2025, 00:42 UTC

WeaknessesCWE-80

Technical details

References

Community reviews

Related threats