S4Nso

**Name of the Vulnerable Software and Affected Versions** SillyTavern versions prior to 1.18.0 **Description** An issue exists in the "/api/extensions/delete" endpoint where it accepts the value "." for the `extensionName` variable. This bypasses the `sanitize-filename` validation, which converts the dot to an empty string, causing the application to resolve the path to the base extensions directory. Consequently, the entire user extensions directory is recursively deleted. In the default configuration, no authentication is required to perform this action. Similar behavior is also present in the "/api/extensions/update", "/api/extensions/version", "/api/extensions/branches", and "/api/extensions/switch" endpoints. **Recommendations** Update to version 1.18.0. As a temporary workaround, restrict network access to the SillyTavern instance to prevent unauthorized requests to the affected API endpoints.

**Name of the Vulnerable Software and Affected Versions** n8n-mcp versions prior to 2.47.11 **Description** When running in HTTP transport mode, incoming requests to the 'POST /mcp' endpoint have their request metadata written to server logs regardless of whether authentication is successful. This can lead to the disclosure of sensitive information in environments where logs are collected or forwarded to external systems, such as SIEM pipelines or shared storage. Exposed data may include bearer tokens from the `Authorization` header, per-tenant API keys from the `x-n8n-key` header in multi-tenant configurations, and JSON-RPC request payloads. While unauthenticated requests are correctly rejected with a 401 Unauthorized response, the sensitive values from these requests are still persisted in the logs. **Recommendations** Update to version 2.47.11 or later. Restrict network access to the HTTP port using a firewall, reverse proxy, or VPN to ensure only trusted clients can reach the endpoint. Switch to stdio transport by setting `MCP MODE=stdio` to eliminate the HTTP surface.

Name of the Vulnerable Software and Affected Versions Postiz versions prior to 2.21.5 Description Postiz, an AI social media scheduling tool, has a Server-Side Request Forgery (SSRF) issue in the `/api/public/stream` endpoint. The application validates the initial URL but does not re-validate the final destination after HTTP redirects. This allows an attacker to provide a public HTTPS URL that passes initial validation and then redirects the server-side request to an internal resource. Recommendations Update to version 2.21.5 or later.