CVE-2025-13702: IBM Sterling Partner Engagement Manager Cross-Site Scripting
IBM Sterling Partner Engagement Manager 6.2.3.0 through 6.2.3.5 and 6.2.4.0 through 6.2.4.2 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.
Security readout for executives and security teams
Plain-English summary
IBM Sterling Partner Engagement Manager has a cross-site scripting flaw that could let malicious JavaScript run in a trusted Web UI session. The cited impact is possible credential disclosure and UI tampering. This is a moderate business risk, especially where partner-management users handle sensitive credentials or external workflows.
Executive priority
Treat this as a scheduled but prompt remediation item. Escalate priority if the Web UI is externally reachable, widely accessible, or used for credentials and partner onboarding workflows.
Technical view
CVE-2025-13702 is CWE-79 XSS in IBM Sterling Partner Engagement Manager 6.2.3.0 through 6.2.3.5 and 6.2.4.0 through 6.2.4.2. CVSS is 6.1, network exploitable, low complexity, user interaction required, changed scope, low confidentiality and integrity impact, no availability impact.
Likely exposure
Organizations running affected IBM Sterling Partner Engagement Manager Standard or Essentials versions are exposed, particularly if the Web UI is reachable by broad internal, partner, or internet-facing user populations.
Exploitation context
The bundle does not show CISA KEV listing or cited active exploitation. It describes authenticated JavaScript embedding in the Web UI and requires user interaction per CVSS, but provides no endpoint, parameter, proof of concept, or exploitation telemetry.
Researcher notes
The source says an authenticated user can embed JavaScript, while the provided CVSS vector lists PR:N. Validate privilege assumptions against IBM guidance. Public details are limited to product ranges, CWE, impact, and vendor advisory reference.
Mitigation direction
Review IBM advisory 7263391 for fixed levels and installation instructions.
Apply IBM-provided patches or upgrades for affected 6.2.3.x and 6.2.4.x deployments.
Restrict Web UI access to trusted networks and required users.
Monitor for suspicious Web UI content changes or unexpected credential prompts.
Confirm session and cookie protections align with IBM guidance.
Validation and detection
Inventory IBM Sterling Partner Engagement Manager versions and editions.
Compare deployed versions against 6.2.3.0-6.2.3.5 and 6.2.4.0-6.2.4.2.
Confirm patch status against IBM advisory 7263391.
Review access paths to the Web UI, including partner and remote access.
Check logs or change records for unusual UI modifications.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.