CVE-2025-54994: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in akoskm create-mcp-server-stdio
@akoskm/create-mcp-server-stdio is an MCP server starter kit that uses the StdioServerTransport. Prior to version 0.0.13, the MCP Server is written in a way that is vulnerable to command injection vulnerability attacks as part of some of its MCP Server tool definition and implementation. The MCP Server exposes the tool `which-app-on-port` which relies on Node.js child process API `exec` which is an unsafe and vulnerable API if concatenated with untrusted user input. Version 0.0.13 contains a fix for the issue.
AI Analysis
Technical Summary
CVE-2025-54994 is a critical security vulnerability classified under CWE-78, which pertains to improper neutralization of special elements used in OS command execution, commonly known as OS Command Injection. This vulnerability affects versions of the Node.js-based package '@akoskm/create-mcp-server-stdio' prior to 0.0.13. The package serves as a starter kit for MCP (Modular Control Protocol) servers using the StdioServerTransport. The vulnerability arises from the exposure of a tool named 'which-app-on-port' that internally uses the Node.js child process API 'exec' to execute system commands. The 'exec' function is inherently unsafe when concatenated with untrusted user input, as it allows an attacker to inject arbitrary commands that the operating system will execute. This can lead to full system compromise, unauthorized data access, or disruption of services. The issue was addressed in version 0.0.13 by presumably sanitizing inputs or replacing unsafe command execution methods. The CVSS 4.0 base score of 9.3 reflects the critical nature of this flaw, with metrics indicating network attack vector, no required privileges or user interaction, and high impact on confidentiality, integrity, and availability. No known exploits are currently reported in the wild, but the ease of exploitation and severity make it a significant threat to any deployment using vulnerable versions of this package.
Potential Impact
For European organizations, the impact of this vulnerability can be severe, especially for those relying on the '@akoskm/create-mcp-server-stdio' package in their MCP server implementations. Successful exploitation could allow attackers to execute arbitrary OS commands remotely without authentication, leading to potential data breaches, service outages, or lateral movement within networks. This is particularly concerning for industries with critical infrastructure or sensitive data, such as finance, healthcare, and manufacturing. The compromise of MCP servers could disrupt operational technology environments or control systems, which are increasingly integrated with IT networks in Europe. Additionally, organizations subject to strict data protection regulations like GDPR could face legal and financial repercussions if this vulnerability leads to unauthorized data disclosure or service disruption. The absence of known exploits in the wild suggests a window of opportunity for proactive patching before widespread attacks occur.
Mitigation Recommendations
European organizations should immediately audit their use of the '@akoskm/create-mcp-server-stdio' package and identify any deployments running versions prior to 0.0.13. The primary mitigation is to upgrade to version 0.0.13 or later, which contains the fix for this vulnerability. If upgrading is not immediately feasible, organizations should implement input validation and sanitization on any user inputs that interact with the 'which-app-on-port' tool or any similar command execution functionality. Restricting network access to MCP servers to trusted hosts and employing application-layer firewalls can reduce exposure. Additionally, monitoring and logging command execution attempts and anomalous activities on affected servers can help detect exploitation attempts. Organizations should also review their incident response plans to include scenarios involving OS command injection attacks and ensure timely patch management processes are in place to prevent exploitation.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Sweden, Poland
CVE-2025-54994: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in akoskm create-mcp-server-stdio
Description
@akoskm/create-mcp-server-stdio is an MCP server starter kit that uses the StdioServerTransport. Prior to version 0.0.13, the MCP Server is written in a way that is vulnerable to command injection vulnerability attacks as part of some of its MCP Server tool definition and implementation. The MCP Server exposes the tool `which-app-on-port` which relies on Node.js child process API `exec` which is an unsafe and vulnerable API if concatenated with untrusted user input. Version 0.0.13 contains a fix for the issue.
AI-Powered Analysis
Technical Analysis
CVE-2025-54994 is a critical security vulnerability classified under CWE-78, which pertains to improper neutralization of special elements used in OS command execution, commonly known as OS Command Injection. This vulnerability affects versions of the Node.js-based package '@akoskm/create-mcp-server-stdio' prior to 0.0.13. The package serves as a starter kit for MCP (Modular Control Protocol) servers using the StdioServerTransport. The vulnerability arises from the exposure of a tool named 'which-app-on-port' that internally uses the Node.js child process API 'exec' to execute system commands. The 'exec' function is inherently unsafe when concatenated with untrusted user input, as it allows an attacker to inject arbitrary commands that the operating system will execute. This can lead to full system compromise, unauthorized data access, or disruption of services. The issue was addressed in version 0.0.13 by presumably sanitizing inputs or replacing unsafe command execution methods. The CVSS 4.0 base score of 9.3 reflects the critical nature of this flaw, with metrics indicating network attack vector, no required privileges or user interaction, and high impact on confidentiality, integrity, and availability. No known exploits are currently reported in the wild, but the ease of exploitation and severity make it a significant threat to any deployment using vulnerable versions of this package.
Potential Impact
For European organizations, the impact of this vulnerability can be severe, especially for those relying on the '@akoskm/create-mcp-server-stdio' package in their MCP server implementations. Successful exploitation could allow attackers to execute arbitrary OS commands remotely without authentication, leading to potential data breaches, service outages, or lateral movement within networks. This is particularly concerning for industries with critical infrastructure or sensitive data, such as finance, healthcare, and manufacturing. The compromise of MCP servers could disrupt operational technology environments or control systems, which are increasingly integrated with IT networks in Europe. Additionally, organizations subject to strict data protection regulations like GDPR could face legal and financial repercussions if this vulnerability leads to unauthorized data disclosure or service disruption. The absence of known exploits in the wild suggests a window of opportunity for proactive patching before widespread attacks occur.
Mitigation Recommendations
European organizations should immediately audit their use of the '@akoskm/create-mcp-server-stdio' package and identify any deployments running versions prior to 0.0.13. The primary mitigation is to upgrade to version 0.0.13 or later, which contains the fix for this vulnerability. If upgrading is not immediately feasible, organizations should implement input validation and sanitization on any user inputs that interact with the 'which-app-on-port' tool or any similar command execution functionality. Restricting network access to MCP servers to trusted hosts and employing application-layer firewalls can reduce exposure. Additionally, monitoring and logging command execution attempts and anomalous activities on affected servers can help detect exploitation attempts. Organizations should also review their incident response plans to include scenarios involving OS command injection attacks and ensure timely patch management processes are in place to prevent exploitation.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2025-08-04T17:34:24.420Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 68bf3299d5a2966cfc82d270
Added to database: 9/8/2025, 7:46:33 PM
Last enriched: 9/8/2025, 8:01:23 PM
Last updated: 10/29/2025, 9:50:42 AM
Views: 87
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-12450: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in litespeedtech LiteSpeed Cache
MediumCVE-2025-64291: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in Premmerce Premmerce User Roles
UnknownCVE-2025-64290: Cross-Site Request Forgery (CSRF) in Premmerce Premmerce Product Search for WooCommerce
UnknownCVE-2025-64289: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in Premmerce Premmerce Product Search for WooCommerce
UnknownCVE-2025-64286: Cross-Site Request Forgery (CSRF) in WpEstate WP Rentals
UnknownActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.