CVE-2024-49339
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 · uneditedIBM Financial Transaction Manager for SWIFT Services for Multiplatforms 3.2.4.0 through 3.2.4.1 is vulnerable to stored cross-site scripting. This vulnerability allows authenticated users 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 confidenceIBM Financial Transaction Manager for SWIFT Services for Multiplatforms versions 3.2.4.0-3.2.4.1 contains a stored XSS vulnerability where authenticated users can inject arbitrary JavaScript into the Web UI. This malicious script persists and executes when other users interact with the affected interface elements, potentially exposing credentials or session tokens within trusted sessions.
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>= 3.2.4.0, <= 3.2.4.13CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed IBM Financial Transaction Manager versionLocate the FTM installation directory and check the version manifest or product-info file. On Linux/Unix, this is typically in /opt/IBM/FTM or the installation root directory. Look for version.info, install.xml, or similar metadata files that contain the product version string.Affected if The installed version falls within 3.2.4.0 through 3.2.4.13 inclusive
-
Confirm Web UI component is enabledCheck the IBM FTM configuration for the Web UI service. Look for configuration files such as server.xml, web.xml, or FTM-specific configuration in the installation directory that controls the Web UI (often named something like ftm-webui-config.xml). Verify the WebApplication or UI service status is set to enabled.Affected if The Web UI service is enabled and accessible
-
Verify Web UI is network-accessibleCheck network listeners and ports configured for FTM Web UI. Review httpd.conf, plugin-cfg.xml, or the IBM HTTP Server configuration if fronting the FTM UI. Confirm the UI is bound to a reachable network interface rather than localhost only.Affected if The Web UI is exposed on a network interface accessible to users
-
Confirm user authentication is enabled for Web UIExamine the Web UI security configuration to verify that authentication is required for access. Check for JAAS configuration, LDAP integration, or other authentication settings in the FTM Web UI configuration files.Affected if Authenticated users can access the Web UI interface where content injection can occur
A defender is affected if their IBM Financial Transaction Manager installation is version 3.2.4.0 through 3.2.4.13 AND the Web UI is enabled and accessible to authenticated users.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply IBM's patched version when available and implement output encoding/validation for user-supplied content in the Web UI to prevent script execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49339 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-49339 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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