dbcve.org
Sterling Partner Engagement ManagerApplication · Ibm

CVE-2025-13702

MEDIUM · 5.4 CVSS v3.1 Published 2026-03-13
Fix available
A fix is available. Upgrade to 6.2.3.6 / 6.2.4.3 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
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.

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 confidence

This is a stored XSS vulnerability in IBM Sterling Partner Engagement Manager's Web UI. An authenticated attacker can inject malicious JavaScript code into the Web interface that executes in other users' browsers within trusted sessions, potentially leading to credential theft or session hijacking.

MitigationApply vendor patches when available. In the interim, implement robust input validation and output encoding across all user-controlled fields, and consider deploying Content Security Policy (CSP) headers to mitigate XSS execution.

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
Sterling Partner Engagement ManagerApplication
Affected:>= 6.2.3, < 6.2.3.6>= 6.2.4, < 6.2.4.3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed version of IBM Sterling Partner Engagement Manager
    Locate the product version information in the system properties, about page, or installation directory. Common locations include the admin console, version.info file, or system configuration files.
    Affected if The installed version falls within 6.2.3.0 through 6.2.3.5, or 6.2.4.0 through 6.2.4.2.
  2. Confirm the Web UI component is enabled
    Check the application configuration to verify that the Web-based user interface is active. This may be visible in the services list, application server configuration, or network listener status.
    Affected if The Web UI is exposed and accessible to users.
  3. Verify user authentication is configured for the Web UI
    Review the authentication settings for the Web interface to confirm that login capabilities are available, as the vulnerability requires an authenticated attacker.
    Affected if User authentication is enabled for the Web interface.
  4. Identify user-controlled input fields in the Web UI
    Examine the Web application forms and input points where users can submit data, particularly in partner-facing or administrative interfaces.
    Affected if The application accepts user input that gets stored and rendered back to other users without proper encoding.

Your environment is affected if IBM Sterling Partner Engagement Manager is running with the Web UI enabled and the installed version is 6.2.3.x before 6.2.3.6, or 6.2.4.x before 6.2.4.3.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.2.3.6 / 6.2.4.3 or later
Fixed in 6.2.3.66.2.4.3
Interim mitigation

Apply vendor patches when available. In the interim, implement robust input validation and output encoding across all user-controlled fields, and consider deploying Content Security Policy (CSP) headers to mitigate XSS execution.

Recommended fix Moderate confidence

6.2.4.3 (or 6.2.3.6 - both contain the fix; 6.2.4.3 is the latest fixed release)

  1. 1. Back up your current IBM Sterling Partner Engagement Manager installation and database.
  2. 2. Download the fixed version from IBM Fix Central or through your IBM support channel.
  3. 3. Select the appropriate fixed version for your current release: upgrade to 6.2.3.6 (if on 6.2.3.x line) or 6.2.4.3 (if on 6.2.4.x line).
  4. 4. Apply the upgrade following IBM's standard upgrade procedures for Sterling Partner Engagement Manager.
  5. 5. After upgrade, clear browser cache and verify the XSS vulnerability is resolved by testing that user-supplied script cannot be executed in the Web UI.
  6. 6. Confirm the installed version matches the expected fixed release.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sterling Partner Engagement Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13702 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13702 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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