dbcve.org
Financial Transaction Manager For MultiplatformApplication · Ibm

CVE-2025-36148

MEDIUM · 6.1 CVSS v3.1 Published 2026-05-26
Fix available
A fix is available. Upgrade to 3.2.4.16 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Financial Transaction Manager for SWIFT Services for Multiplatforms 3.2.4.0 through 3.2.4.15 IBM Financial Transaction Manager SWIFT is vulnerable to cross-site scripting. This vulnerability allows an unauthenticated attacker 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

IBM Financial Transaction Manager for SWIFT Services contains a reflected cross-site scripting (XSS) vulnerability in its Web UI. An unauthenticated attacker can inject arbitrary JavaScript code through unsanitized input, which executes within the context of a trusted user session, potentially leading to credential disclosure or session hijacking.

MitigationApply IBM's security patch for this vulnerability (versions beyond 3.2.4.15) and implement output encoding and input validation on all user-supplied data in the web interface.

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
Financial Transaction Manager For MultiplatformApplication
Affected:>= 3.2.4.0, < 3.2.4.16

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 IBM FTM for SWIFT installation
    Locate the IBM Financial Transaction Manager for SWIFT Services for Multiplatforms installation directory or check installed packages using the system package manager. Common locations include /opt/ibm/ftm or the installation path configured during setup.
    Affected if The product is installed on the system
  2. Determine installed version
    Check the product version by inspecting version files, About dialog in the Web UI, or using the product's built-in version command if available. Compare the version number against the affected range 3.2.4.0 through 3.2.4.15.
    Affected if The installed version is 3.2.4.0 through 3.2.4.15 inclusive
  3. Verify Web UI is accessible
    Confirm the IBM FTM Web UI component is enabled and network-accessible by attempting to reach the Web UI endpoint (typically on port 9443 or 443). Check if the UI responds to authentication requests.
    Affected if The Web UI is exposed and accepts user authentication
  4. Check for XSS indicators in logs
    Review IBM FTM Web UI and application server logs (such as WebSphere or the embedded server logs) for any suspicious script tags, JavaScript code, or unexpected HTML in user input fields, transaction data, or admin-configurable fields.
    Affected if Logs contain unsanitized script tags or JavaScript code in user-supplied fields

You are affected if IBM Financial Transaction Manager for SWIFT Services for Multiplatforms version 3.2.4.0 through 3.2.4.15 is installed and its Web UI component is accessible to users.

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 3.2.4.16 or later
Fixed in 3.2.4.16
Interim mitigation

Apply IBM's security patch for this vulnerability (versions beyond 3.2.4.15) and implement output encoding and input validation on all user-supplied data in the web interface.

Recommended fix Moderate confidence

IBM Financial Transaction Manager for Multiplatform version 3.2.4.16

  1. Confirm current installed version of IBM Financial Transaction Manager for Multiplatform
  2. Obtain IBM Financial Transaction Manager for Multiplatform version 3.2.4.16 from IBM Fix Central or official IBM support channels
  3. Follow IBM documentation to apply the version 3.2.4.16 update to your installation
  4. Verify the update was applied successfully and the version is now 3.2.4.16
  5. Test the Web UI functionality to ensure the XSS vulnerability is remediated

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

Fix this in Financial Transaction Manager For Multiplatform Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-36148 — 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-36148 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