CVE-2025-36033VulnerabilityPublished 3 Feb 2026

CVE-2025-36033: IBM Engineering Lifecycle Management – Global Configuration Management · Cross-site Scripting

Affects IBM Engineering Lifecycle Management – Global Configuration ManagementSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.4Medium

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% 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 3 Feb 2026
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 2026-10-26.

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 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
IBMEngineering Lifecycle Management - Global Configuration Management	Affected =7.0.3 =7.1.0	Fixed in–

CPE configurations (4)

cpe:2.3:a:ibm:engineering_lifecycle_management___global_configuration_management:7.0.3:*:*:*:*:*:*:*
cpe:2.3:a:ibm:engineering_lifecycle_management___global_configuration_management:7.0.3:interim_fix_017:*:*:*:*:*:*
cpe:2.3:a:ibm:engineering_lifecycle_management___global_configuration_management:7.1.0:*:*:*:*:*:*:*
cpe:2.3:a:ibm:engineering_lifecycle_management___global_configuration_management:7.1.0:interim_fix_004:*:*:*:*:*:*

AI-suggested

To mitigate CVE-2025-36033, European organizations should: 1) Monitor IBM's official channels for patches or interim fixes and apply them promptly once available. 2) Implement strict input validation and output encoding on all user-supplied data within the IBM ELM Global Configuration Management interface to prevent script injection. 3) Restrict user privileges to the minimum necessary, limiting the number of users who can access or modify configuration management settings. 4) Enforce multi-factor authentication (MFA) to reduce the risk of credential compromise. 5) Conduct regular security training to raise awareness about phishing and social engineering that could facilitate exploitation. 6) Monitor web UI logs and network traffic for unusual activities indicative of XSS exploitation attempts. 7) Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in the web interface. 8) Isolate the IBM ELM environment within secure network segments to limit lateral movement if credentials are compromised. 9) Review and harden session management controls to prevent session hijacking. These measures collectively reduce the attack surface and limit the potential damage from exploitation.

Description

CVE-2025-36033 is a medium severity cross-site scripting (XSS) vulnerability in IBM Engineering Lifecycle Management - Global Configuration Management versions 7.0.3 through 7.0.3 Interim Fix 017 and 7.1.0 through 7.1.0 Interim Fix 004. It allows an authenticated user to inject arbitrary JavaScript into the web interface, potentially altering functionality and leading to credential disclosure within trusted sessions.

Impact

For European organizations, the impact of CVE-2025-36033 can be significant in sectors relying on IBM Engineering Lifecycle Management for software development and configuration management, such as aerospace, automotive, telecommunications, and defense. Successful exploitation could lead to unauthorized disclosure of credentials, enabling attackers to impersonate legitimate users and potentially gain broader access to sensitive project data and intellectual property. This could result in data breaches, intellectual property theft, and disruption of software development workflows. Given the medium severity and requirement for authentication, the threat is more pronounced in large organizations with many users and complex access rights. Additionally, compromised credentials could facilitate further attacks within the network, increasing the risk of supply chain attacks or sabotage. The vulnerability does not directly affect availability but undermines confidentiality and integrity, which are critical for maintaining trust and compliance with European data protection regulations such as GDPR. Organizations with stringent compliance requirements must address this vulnerability promptly to avoid regulatory and reputational damage.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
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)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

CPE configurations (4)

Description

AI analysisMachine-generated, updated 11 Feb 2026, 12:09 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats