CyberSecBulletin
CVE-2025-12737NVD status: Analyzed

WSO2 Open Banking AM: Improper Neutralization of Special Elements used in an OS Command

Published Updated By the CyberSecBulletin desk

CVE-2025-12737 is a high-severity improper neutralization of special elements used in an OS command vulnerability in WSO2 Open Banking AM from WSO2, with a CVSS 3.1 base score of 8.4 out of 10. It can be exploited from the same local network by an attacker with administrator privileges, without any action from a user. The record lists version 2.0.0.398 as the first without the flaw, so updating WSO2 Open Banking AM to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.37% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update WSO2 Open Banking AM to 2.0.0.398 or a later version.
  2. Update WSO2 Open Banking IAM to 2.0.0.418 or a later version.
  3. Update WSO2 Traffic Manager to 4.5.0.34 or 4.6.0.1, whichever matches your release line, or a later version.
  4. Read the advisory on security.docs.wso2.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
WSO2WSO2 Open Banking AM2.0.0 up to, but not including, 2.0.0.3982.0.0.398
WSO2WSO2 Open Banking IAM2.0.0 up to, but not including, 2.0.0.4182.0.0.418
WSO2WSO2 Traffic Manager4.5.0 up to, but not including, 4.5.0.34; 4.6.0 up to, but not including, 4.6.0.14.5.0.34, 4.6.0.1
WSO2WSO2 Universal Gateway4.5.0 up to, but not including, 4.5.0.34; 4.6.0 up to, but not including, 4.6.0.14.5.0.34, 4.6.0.1
WSO2WSO2 API Control Plane4.5.0 up to, but not including, 4.5.0.36; 4.6.0 up to, but not including, 4.6.0.14.5.0.36, 4.6.0.1
WSO2WSO2 API Manager3.1.0 up to, but not including, 3.1.0.349; 3.2.0 up to, but not including, 3.2.0.453; 3.2.1 up to, but not including, 3.2.1.73; 4.0.0 up to, but not including, 4.0.0.373; 4.1.0 up to, but not including, 4.1.0.236; 4.2.0 up to, but not including, 4.2.0.176; 4.3.0 up to, but not including, 4.3.0.88; 4.4.0 up to, but not including, 4.4.0.52; and 2 more ranges3.1.0.349, 3.2.0.453, 3.2.1.73, 4.0.0.373, 4.1.0.236, 4.2.0.176
WSO2WSO2 Identity Server as Key Manager5.10.0 up to, but not including, 5.10.0.3695.10.0.369
WSO2WSO2 Identity Server5.10.0 up to, but not including, 5.10.0.378; 5.11.0 up to, but not including, 5.11.0.425; 6.0.0 up to, but not including, 6.0.0.252; 6.1.0 up to, but not including, 6.1.0.253; 7.0.0 up to, but not including, 7.0.0.130; 7.1.0 up to, but not including, 7.1.0.38; 7.2.0 up to, but not including, 7.2.0.15.10.0.378, 5.11.0.425, 6.0.0.252, 6.1.0.253, 7.0.0.130, 7.1.0.38
WSO2API Control Plane4.5.0 up to, but not including, 4.5.0.36; 4.6.04.5.0.36
WSO2API Manager3.1.0 up to, but not including, 3.1.0.349; 3.2.0 up to, but not including, 3.2.0.453; 3.2.1 up to, but not including, 3.2.1.73; 4.0.0 up to, but not including, 4.0.0.373; 4.1.0 up to, but not including, 4.1.0.236; 4.2.0 up to, but not including, 4.2.0.176; 4.3.0 up to, but not including, 4.3.0.88; 4.4.0 up to, but not including, 4.4.0.52; and 2 more ranges3.1.0.349, 3.2.0.453, 3.2.1.73, 4.0.0.373, 4.1.0.236, 4.2.0.176
WSO2Identity Server5.10.0 up to, but not including, 5.10.0.378; 5.11.0 up to, but not including, 5.11.0.425; 6.0.0 up to, but not including, 6.0.0.252; 6.1.0 up to, but not including, 6.1.0.253; 7.0.0 up to, but not including, 7.0.0.130; 7.1.0 up to, but not including, 7.1.0.38; 7.2.05.10.0.378, 5.11.0.425, 6.0.0.252, 6.1.0.253, 7.0.0.130, 7.1.0.38
WSO2Identity Server As Key Manager5.10.0 up to, but not including, 5.10.0.3695.10.0.369
WSO2Open Banking Am2.0.0 up to, but not including, 2.0.0.3982.0.0.398
WSO2Open Banking Iam2.0.0 up to, but not including, 2.0.0.4182.0.0.418
WSO2Traffic Manager4.5.0 up to, but not including, 4.5.0.34; 4.6.04.5.0.34
WSO2Universal Gateway4.5.0 up to, but not including, 4.5.0.34; 4.6.04.5.0.34

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
AdjacentThe attacker must be on the same local network segment.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
HighAdministrator-level access is required first.
User interaction
NoneNo action by a victim is required.
Scope
ChangedThe attack can reach beyond the vulnerable component into other systems.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H. Scored by CNA.

Official description

The administrative operations within the Carbon Console do not adequately validate specific user-supplied input. This oversight allows a malicious actor with administrative privileges to inject and execute arbitrary code remotely. Successful exploitation enables a threat actor with administrative privileges and Carbon Console access to execute remote arbitrary code through specific administrative operations, leading to a complete compromise of the affected system.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Neutralization of Special Elements used in an OS Command

The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command before it is sent to a downstream component.

How developers prevent this class of flaw

  • If at all possible, use library calls rather than external processes to recreate the desired functionality.
  • For any data that will be used to generate a command to be executed, keep as much of that data out of external control as possible. For example, in web applications, this may require storing the data locally in the session's state instead of sending it out to the client in a hidden form field.
  • For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.

More Improper Neutralization of Special Elements used in an OS Command vulnerabilities (CWE-78)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in WSO2 Open Banking AM

All WSO2 Open Banking AM vulnerabilities

Recent Improper Neutralization of Special Elements used in an OS Command vulnerabilities

Spotted an error? Tell us.