CVE-2026-5023
OS Command Injection in DeDeveloper23 RepoMix Command Handler
Publication date: 2026-03-29
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| dedeveloper23 | codebase_mcp | to 1.0.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-77 | The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-5023 is a command injection vulnerability found in the DeDeveloper23 codebase-mcp project, specifically affecting the getCodebase, getRemoteCodebase, and saveCodebase functions in the src/tools/codebase.ts file. The issue arises because these functions use Node.js's child_process.execSync to execute shell commands by directly inserting user-controlled input parameters without proper sanitization.
Since execSync runs commands through a system shell, malicious input containing shell metacharacters (such as ;, &, |) can be interpreted as additional commands, allowing an attacker to execute arbitrary commands on the host system with the privileges of the MCP server process.
The attack requires local access to the system. The vulnerability affects all versions up to and including 1.0.0 of the codebase-mcp project. The problem is worsened in environments where parameters are generated by large language models influenced by external content, potentially triggering command injection without direct user interaction.
How can this vulnerability impact me? :
Successful exploitation of this vulnerability allows an attacker with local access to execute arbitrary operating system commands on the host running the MCP server. This can lead to unauthorized data access, modification of system files, installation of malware, or further compromise of the system depending on the privileges of the MCP server process.
Because the commands run with the MCP server's privileges, the impact can be significant, potentially allowing full control over the affected system.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves command injection through unsafe usage of Node.js's child_process.execSync function in the codebase-mcp project. Detection involves identifying if the vulnerable functions getCodebase, getRemoteCodebase, or saveCodebase are being exploited by observing suspicious command executions or unusual shell commands triggered locally.
Since the attack requires local execution and involves shell metacharacters in input parameters, monitoring logs for commands containing shell metacharacters such as ;, &, | in parameters like includePatterns, ignorePatterns, repo, or outputFile can help detect exploitation attempts.
Suggested commands to detect potential exploitation attempts include searching for suspicious patterns in logs or running processes. For example, on a Linux system, you might use:
- grep -rE '[;&|]' /var/log/* # Search logs for shell metacharacters
- ps aux | grep codebase-mcp # Check running processes for suspicious commands
- auditctl -w /path/to/codebase.ts -p x -k codebase_exec # Set audit rules to monitor execution of the vulnerable file
Additionally, reviewing the codebase.ts file for usage of execSync with untrusted input can help identify vulnerable code.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the vulnerable usage of execSync with execFileSync, which accepts command arguments as an array and prevents shell interpretation of input.
Implement strict input validation and parameter escaping on all client-exposed tool parameters such as includePatterns, ignorePatterns, repo, and outputFile to prevent injection of shell metacharacters.
Limit the privileges of the MCP server process to minimize potential impact if exploitation occurs.
Monitor and audit usage of the vulnerable functions and related files to detect any exploitation attempts.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows for arbitrary command execution on the host server, which can lead to unauthorized data access and system modification.
Such unauthorized access and potential data breaches could negatively impact compliance with data protection standards and regulations like GDPR and HIPAA, which require safeguarding sensitive data and ensuring system integrity.
However, the provided information does not explicitly state the direct impact on compliance with these standards.