232-323

**Name of the Vulnerable Software and Affected Versions** Roslyn CodeLens MCP Server versions 0.0.9 through 1.16.0 **Description** The `get diagnostics` MCP tool loads and executes all DiagnosticAnalyzer assemblies referenced by the target solution without an allowlist, signature check, or user confirmation. Because the `includeAnalyzers` variable defaults to true, no explicit opt-in is required. An attacker can achieve arbitrary code execution in the server process with the server's OS privileges by placing a malicious `.csproj` file that references an attacker-controlled DLL in a location opened by the victim using the MCP server. **Recommendations** Update to version 1.17.0.

**Name of the Vulnerable Software and Affected Versions** Network-AI versions prior to 5.1.3 **Description** The MCP HTTP transport accepts JSON-RPC `tools/call` requests without requiring authentication, sessions, origins, or token checks, dispatching them directly to the orchestrator's tool registry. Because the service binds to `0.0.0.0` by default, any party with network reachability can enumerate and invoke privileged management tools. This allows unauthorized users to read and mutate live orchestrator configurations, list and dispatch agents, create or revoke security tokens, and adjust global budget ceilings. The issue is specifically present in the ` handlePost()` function, which fails to perform authentication checks before calling `handleRPC()`, and the `handleRPC()` function, which dispatches requests to the `call(toolName, toolArgs)` function. **Recommendations** Update to version 5.1.3. As a temporary workaround, restrict access to the `/mcp` endpoint to trusted networks or change the bind address from `0.0.0.0` to `127.0.0.1` to prevent external network exposure.

**Name of the Vulnerable Software and Affected Versions** WeGIA versions prior to 3.2.12 **Description** A SQL Injection vulnerability was discovered in the WeGIA application, "salvar tag.php" endpoint. This vulnerability could allow an authorized attacker to execute arbitrary SQL queries, allowing access to or deletion of sensitive information. **Recommendations** For WeGIA versions prior to 3.2.12, upgrade to version 3.2.12 to resolve the issue. As a temporary workaround, consider restricting access to the "salvar tag.php" endpoint until the upgrade is applied. There are no known workarounds for this vulnerability.