Ameeba Exploit Tracker

Tracking CVEs, exploits, and zero-days for defensive cybersecurity research.

Ameeba Blog Search
TRENDING · 1 WEEK
Attack Vector
Vendor
Severity

CVE-2025-53372: Command Injection Vulnerability in node-code-sandbox-mcp

Ameeba Chat Store screens
Download Ameeba Chat

Overview

The CVE-2025-53372 vulnerability refers to a critical flaw found in the node-code-sandbox-mcp, a Node.js-based Model Context Protocol server. This vulnerability, if successfully exploited, can lead to remote code execution, compromising the host system and potentially leading to data leakage. This vulnerability affects all versions of node-code-sandbox-mcp prior to 1.3.0.

Vulnerability Summary

CVE ID: CVE-2025-53372
Severity: High, CVSS: 7.5
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: Remote Code Execution, Potential System Compromise, and Data Leakage

Affected Products

Ameeba Chat Icon Escape the Surveillance Era

Most apps won’t tell you the truth.
They’re part of the problem.

Phone numbers. Emails. Profiles. Logs.
It’s all fuel for surveillance.

Ameeba Chat gives you a way out.

  • • No phone number
  • • No email
  • • No personal info
  • • Anonymous aliases
  • • End-to-end encrypted

Chat without a trace.

Product | Affected Versions

node-code-sandbox-mcp | < 1.3.0 How the Exploit Works

The vulnerability exists due to the unsanitized use of input parameters within a call to child_process.execSync. This allows an attacker to inject arbitrary system commands. Successful exploitation can lead to remote code execution under the server process’s privileges on the host machine, bypassing the sandbox protection of running code inside docker.

Conceptual Example Code

Here’s a conceptual example of how an attacker might exploit this vulnerability:

// Attacker uses unsanitized input to pass malicious command
var payload = "`touch /tmp/arbitrary-file`";
// The unsanitized input is passed to child_process.execSync
require('child_process').execSync(payload);

In this example, if the payload is executed, an arbitrary file would be created in the /tmp directory, demonstrating the ability to execute arbitrary commands.

Want to discuss this further? Join the Ameeba Cybersecurity Group Chat.

Disclaimer:

The information and code presented in this article are provided for educational and defensive cybersecurity purposes only. Any conceptual or pseudocode examples are simplified representations intended to raise awareness and promote secure development and system configuration practices.

Do not use this information to attempt unauthorized access or exploit vulnerabilities on systems that you do not own or have explicit permission to test.

Ameeba and its authors do not endorse or condone malicious behavior and are not responsible for misuse of the content. Always follow ethical hacking guidelines, responsible disclosure practices, and local laws.
Ameeba Chat