VulnerabilityPublished 17 Feb 2026

CVE-2025-33135: IBM Financial Transaction Manager for ACH Services and Check Services for Multi-Platform · Cross-site Scripting

Affects IBM Financial Transaction Manager for ACH Services and Check Services for Multi-PlatformSource CVE Database V5

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

6.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
IBMFinancial Transaction Manager for ACH Services and Check Services for Multi-Platform	Affected =3.0.0.0	Fixed in–

CPE configurations (2)

cpe:2.3:a:ibm:financial_transaction_manager_for_ach_services_and_check_services_for_multi_platform:3.0.0.0:*:*:*:*:*:*:*
cpe:2.3:a:ibm:financial_transaction_manager_for_ach_services_and_check_services_for_multi_platform:3.0.5.4:interim_fix_027:*:*:*:*:*:*

AI-suggested

To mitigate CVE-2025-33135, organizations should implement the following specific measures: 1) Monitor IBM’s official channels closely for patches or interim fixes and apply them promptly once available. 2) Employ strict input validation and output encoding on all user-supplied data within the IBM Financial Transaction Manager web interface to prevent script injection. 3) Implement Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in the web UI. 4) Conduct regular security assessments and penetration testing focused on web interface vulnerabilities to detect similar issues proactively. 5) Educate users about the risks of interacting with suspicious links or content that could trigger XSS attacks. 6) Use web application firewalls (WAFs) with rules tuned to detect and block XSS payloads targeting the affected applications. 7) Monitor logs and user activity for anomalous behavior indicative of exploitation attempts. 8) Isolate the affected application environment to limit lateral movement in case of compromise. These steps go beyond generic advice by focusing on compensating controls and proactive detection until official patches are released.

Description

IBM Financial Transaction Manager for ACH Services and Check Services for Multi-Platform 3.0.0.0 through 3.0.5.4 Interim Fix 027 IBM Financial Transaction Manager for Check Services v3 (Multiplatforms) 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.

Impact

The impact of this XSS vulnerability on organizations worldwide is significant, especially for financial institutions and enterprises relying on IBM Financial Transaction Manager for ACH and Check Services. Successful exploitation can lead to credential theft, session hijacking, and unauthorized actions within the affected financial applications, potentially resulting in financial fraud, data breaches, and loss of customer trust. Because the vulnerability allows code execution in the context of a trusted session, attackers can bypass some traditional security controls. The lack of authentication requirement lowers the barrier for attackers, increasing the likelihood of exploitation if user interaction occurs. Although availability is not impacted, the confidentiality and integrity of sensitive financial transaction data are at risk. Organizations may face regulatory compliance issues and reputational damage if exploited. The absence of known exploits in the wild currently limits immediate risk but does not preclude future attacks, especially as threat actors often target financial software.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

ibm.com/support/pages/node/7260111 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

CPE configurations (2)

Description

AI analysisMachine-generated, updated 25 Feb 2026, 00:09 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats