Thelicato

**Name of the Vulnerable Software and Affected Versions** Roo Code versions 3.25.23 and below **Description** Roo Code is an AI-powered autonomous coding agent. Versions 3.25.23 and below include `npm install` in a default list of auto-approved commands. Because `npm install` executes lifecycle scripts, a malicious `package.json` file with a malicious `postinstall` script could be executed automatically without user approval, potentially leading to arbitrary code execution. **Recommendations** Update to version 3.26.0 or later.

**Name of the Vulnerable Software and Affected Versions** Roo Code versions 3.25.23 and below **Description** Roo Code, an AI-powered autonomous coding agent, is susceptible to a flaw where VS Code workspace configuration files (.code-workspace) lack the same protection as files within the .vscode folder. If the agent is configured for auto-approval of file writes, an attacker leveraging prompt injection could introduce malicious workspace settings or tasks. Upon reopening the workspace, these tasks could execute arbitrary code. **Recommendations** Update to version 3.26.0 or later.

**Name of the Vulnerable Software and Affected Versions** Roo Code versions 3.25.23 and below **Description** Roo Code, an AI-powered autonomous coding agent, is susceptible to a bypass of its `.rooignore` protections when using symlinks. This allows an attacker with write access to the workspace to read files intended to be excluded. Consequently, sensitive files, such as `.env` or configuration files, could be exposed. An attacker modifying files within the workspace could gain unauthorized access to sensitive information by circumventing `.rooignore` rules, potentially including secrets and configuration details. **Recommendations** Update to version 3.26.0 or later.

**Name of the Vulnerable Software and Affected Versions** SearchWP Live Ajax Search WordPress plugin versions prior to 1.6.2 **Description** The issue allows unauthenticated users to make a crafted query, disclosing private, draft, and pending post titles along with their permalinks, because it does not limit live search results to published posts only. **Recommendations** For versions prior to 1.6.2, update to version 1.6.2 or later to resolve the issue. As a temporary workaround, consider restricting access to the live search functionality until the update is applied.