CVE-2025-33128: IBM Engineering Workflow Management XSS Vulnerability – Patch & Detection Guide
IBM Engineering Workflow Management contains a stored cross-site scripting (XSS) vulnerability that allows authenticated users to inject malicious JavaScript into the Web UI. An attacker with valid credentials could craft a payload that executes in the browser of other users viewing the same application, potentially stealing session credentials or performing unauthorized actions on their behalf. The vulnerability requires user interaction (a victim must view the attacker's injected content) but spreads through a trusted application interface, making it a meaningful risk in collaborative engineering environments.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 5.4 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
- Weaknesses (CWE)
- CWE-79
- Affected products
- 29 configuration(s)
- Published / Modified
- 2026-06-22 / 2026-06-26
NVD description (verbatim)
IBM Engineering Workflow Management 7.0.3 through 7.0.3 Interim Fix 020, and 7.1 through 7.1 Interim Fix 007 is vulnerable to cross-site scripting. This vulnerability allows an authenticated user to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
This is a reflected or stored XSS vulnerability (CWE-79) affecting IBM Engineering Workflow Management versions 7.0.3 through 7.0.3 Interim Fix 020 and 7.1 through 7.1 Interim Fix 007. The vulnerability stems from insufficient input sanitization or output encoding in the Web UI, allowing authenticated attackers to embed arbitrary JavaScript that executes in the context of other users' sessions. The CVSS 3.1 score of 5.4 (Medium) reflects the requirement for prior authentication and user interaction, coupled with potential for credential disclosure and UI manipulation within a broader scope (cross-site impact).
Business impact
For organizations running Engineering Workflow Management in collaborative environments, this vulnerability creates an insider threat vector. Authenticated users—whether employees, contractors, or compromised accounts—can embed malicious payloads in shared documents, comments, or data fields. When colleagues access that content, their session cookies or authentication tokens become vulnerable to theft. In engineering contexts where project data and intellectual property are sensitive, credential compromise could lead to unauthorized access escalation, data exfiltration, or tampering with design artifacts. The trust placed in the application as a central repository amplifies the risk.
Affected systems
IBM Engineering Workflow Management 7.0.3 up to and including Interim Fix 020, and version 7.1 up to and including Interim Fix 007 are vulnerable. Organizations running earlier or later versions should verify their deployment status against IBM's security advisories. The vulnerability is specific to the Web UI, so deployments relying solely on non-web integrations may have reduced exposure, though this should not be assumed without explicit confirmation.
Exploitability
Exploitation requires valid application credentials, making opportunistic external attacks unlikely. However, the barrier is low for insider threats, disgruntled employees, or attackers who have compromised a low-privileged account. Once authenticated, crafting and injecting XSS payloads is relatively straightforward. The need for a victim to view the malicious content introduces some friction, but in shared engineering tools where team members routinely browse project updates and comments, such interaction is highly probable. No exploit code or automated tools have been publicly disclosed, but this is a well-understood attack class.
Remediation
Apply the latest interim fixes or patches released by IBM for your version line. For 7.0.3 users, upgrade beyond Interim Fix 020; for 7.1 users, upgrade beyond Interim Fix 007. Verify patch availability and compatibility through IBM's support portal before deployment. If patches are not immediately available, implement network controls to restrict access to the Web UI to trusted networks or users, and consider disabling automated trust in session cookies (e.g., requiring re-authentication for sensitive operations).
Patch guidance
Contact IBM support or check the IBM Engineering Workflow Management security advisories page to obtain the appropriate interim fix or service release for your version. Test patches in a non-production environment to confirm compatibility with your workflow customizations and integrations. Interim fixes are typically cumulative, so the latest available fix for your version line should be prioritized. Establish a change control process to schedule patching during a maintenance window that minimizes business disruption. Verify successful patching by confirming the installed version matches or exceeds the remediated level.
Detection guidance
Monitor Web UI access logs for unusual patterns: rapid successive requests with different content types, requests containing suspicious parameter values with HTML/JavaScript syntax, or POST requests to form submission endpoints from unexpected sources. Web application firewalls (WAF) configured with XSS detection rules should flag attempts to inject script tags or event handlers. Correlate successful injections with subsequent login anomalies or token usage from unexpected IP addresses. Review recent changes to shared documents, comments, or custom fields in Engineering Workflow Management for suspicious markup or unusual encoding patterns. If using Security Information and Event Management (SIEM), create correlation rules linking XSS-pattern detections to authentication events from different IPs within short time windows.
Why prioritize this
Although the CVSS score is Medium (5.4), the risk is elevated by context. Engineering Workflow Management is a high-value collaborative platform in organizations that rely on it; breach of its integrity or user credentials represents significant operational and intellectual property risk. The authenticated-only requirement and user interaction factor prevent this from being Critical, but the likelihood of exploitation within a trusted environment and the sensitivity of engineering data warrant prioritization above the numeric score alone. Organizations with multi-tenant or contractor access should treat this as higher priority.
Risk score, explained
The CVSS 3.1 base score of 5.4 reflects: (1) Network attack vector (exploitable remotely if the application is internet-facing), (2) Low attack complexity (no special conditions required beyond authentication), (3) Low privilege requirement (any authenticated user can inject), (4) Required user interaction (victim must view the payload), (5) Changed scope (XSS can affect other users' sessions and the integrity of the application UI), and (6) Low confidentiality impact (credential theft is possible but not guaranteed). The absence of availability impact keeps it from reaching High or Critical. Context-specific factors—such as the application's prominence in your organization, exposure to untrusted accounts, and data sensitivity—may warrant treating your instance as higher priority than the base score suggests.
Frequently asked questions
Can this vulnerability be exploited without a valid user account?
No. The vulnerability requires prior authentication to the Web UI. Unauthenticated attackers cannot directly inject payloads. However, compromised accounts, insider threats, or accounts provisioned to contractors increase the risk surface.
What is the difference between the 7.0.3 and 7.1 fix versions I need to apply?
The vulnerability affects both version lines but at different interim fix thresholds. For 7.0.3, you must move beyond Interim Fix 020; for 7.1, beyond Interim Fix 007. Check IBM's advisories to confirm the exact patch build numbers for your deployment, as interim fix naming may vary.
If we restrict Web UI access to our internal network, are we protected?
Network restriction significantly reduces exposure by limiting who can authenticate, but it is not a complete remedy. Insiders and network-adjacent threats remain capable of exploitation. Apply patches as the primary control; network restriction is a supplementary hardening measure.
Could this vulnerability allow an attacker to steal my password directly?
Not directly. XSS in this context can steal session cookies or tokens that represent your logged-in state, allowing the attacker to impersonate you without needing your password. Changing your password does not invalidate stolen cookies if they have long expiration times, so also revoke sessions and review account activity if compromise is suspected.
This analysis is provided for informational purposes to assist security decision-making. It does not constitute legal, compliance, or professional security advice. Readers are responsible for verifying all technical details, patch availability, and version applicability against official IBM security advisories and their own system configurations before taking remedial action. SEC.co makes no warranty regarding the accuracy or completeness of this content and assumes no liability for decisions made based on it. Always test patches in non-production environments and consult with your vendor and internal security teams before deployment. Source: NVD (public-domain), retrieved 2026-07-28. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-11372MEDIUMIBM TRIRIGA XSS Vulnerability – Patch Guidance and Detection
- CVE-2016-20070MEDIUMPrivilege Escalation & Stored XSS in WordPress Booking Calendar Contact Form 1.0.23
- CVE-2018-25384MEDIUMStored XSS in Wikidforum 2.20 Allows Authenticated Attackers to Inject Malicious Scripts
- CVE-2019-25731MEDIUMStored XSS in Zuz Music 2.1 Contact Form
- CVE-2019-25737MEDIUMStored XSS in Live Chat Unlimited 2.8.3 – Admin Session Compromise
- CVE-2019-25739MEDIUMGigToDo 1.3 Stored XSS Vulnerability in Proposal Descriptions
- CVE-2019-25742MEDIUMStored XSS in Zoner Real Estate WordPress Theme 4.1.1 – Admin Account Compromise Risk
- CVE-2019-25743MEDIUMWordPress Soliloquy Lite 2.5.6 Stored XSS Vulnerability