WSO2 Integrator up to 4.1.3 MI for Visual Studio Code os command injection

Summaryinfo

A vulnerability marked as problematic has been reported in WSO2 Integrator up to 4.1.3. This affects an unknown function of the component MI for Visual Studio Code. The manipulation leads to os command injection. This vulnerability is listed as CVE-2026-19515. The attack must be carried out locally. There is no available exploit.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in WSO2 Integrator up to 4.1.3. This issue affects an unknown code of the component MI for Visual Studio Code. The manipulation with an unknown input leads to a os command injection vulnerability. Using CWE to declare the problem leads to CWE-78. 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 when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

The WSO2 Integrator MI VS Code extension fails to properly sanitize or validate user-supplied input when processing Micro Integrator projects opened from untrusted sources. This allows a crafted project to inject and execute arbitrary operating system commands through the unit test execution flow. Successful exploitation of this vulnerability could lead to the execution of arbitrary OS commands on the system where the VS Code extension is running. The extent of the impact is dependent on the privileges of the user account under which VS Code is operating. Exploitation requires the user to grant workspace trust to the malicious project and subsequently trigger the unit test execution.

The advisory is shared at security.docs.wso2.com. The identification of this vulnerability is CVE-2026-19515 since 08/11/2026. The exploitation is known to be easy. An attack has to be approached locally. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1202 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• WSO2

Name

• Integrator

Version

• 4.1.0
• 4.1.1
• 4.1.2
• 4.1.3

License

• commercial

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion