A vulnerability was detected in JoeCastrom mcp-chat-studio up to 1.5.0. Affected by this issue is some unknown functionality of the file server/routes/llm.js of the component LLM Models API. Performing a manipulation of the argument req.query.base_url results in server-side request forgery. Remote exploitation of the attack is possible. The exploit is now public and may be used. The project was informed of the problem early through an issue report but has not responded yet.
A security vulnerability has been detected in AlejandroArciniegas mcp-data-vis up to de5a51525a69822290eaee569a1ab447b490746d. Affected by this vulnerability is the function axios of the file src/servers/web-scraper/server.js of the component HTTP Request Handler. Such manipulation leads to server-side request forgery. The attack may be launched remotely. The exploit has been disclosed publicly and may be used. This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases. The project was informed of the problem early through an issue report but has not responded yet.
CyberPanel versions prior to 2.4.5 contain a stored cross-site scripting vulnerability in the AI Scanner dashboard where the POST /api/ai-scanner/callback endpoint lacks authentication and allows unauthenticated attackers to inject malicious JavaScript by overwriting the findings_json field of ScanHistory records. Attackers can inject JavaScript that executes in an administrator's authenticated session when they visit the AI Scanner dashboard, allowing them to issue same-origin requests to plant cron jobs and achieve remote code execution on the server.
@astrojs/cloudflare versions prior to 13.1.10 contain a Server-Side Request Forgery (SSRF) vulnerability. The issue arises because the fetch() call for remote images follows HTTP redirects by default, allowing redirection to arbitrary URLs. This behavior bypasses the domain allowlist check, which only validates the initial URL, potentially enabling SSRF attacks. This vulnerability is a regression from an incomplete fix for CVE-2025-58179 and has been addressed in version 13.1.10.
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, a Server-Side Request Forgery (SSRF) protection bypass vulnerability exists in the Custom Function feature. While the application implements SSRF protection via HTTP_DENY_LIST for axios and node-fetch libraries, the built-in Node.js http, https, and net modules are allowed in the NodeVM sandbox without equivalent protection. This allows authenticated users to bypass SSRF controls and access internal network resources (e.g., cloud provider metadata services) This vulnerability is fixed in 3.1.0.
FlowiseAI Flowise versions prior to 3.1.0 contain a vulnerability that allows unrestricted upload of JavaScript files by modifying the Chatflow configuration file upload settings. This enables attackers to upload malicious Node.js web shells to the server, potentially leading to remote code execution. The vulnerability is identified as CWE-434 and has a CVSS score of 7.1, indicating high severity. A fix for this issue is available in version 3.1.0.
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, an improper mass assignment (JSON injection) vulnerability in the account registration endpoint of Flowise Cloud allows unauthenticated attackers to inject server-managed fields and nested objects during account creation. This enables client-controlled manipulation of ownership metadata, timestamps, organization association, and role mappings, breaking trust boundaries in a multi-tenant environment. This vulnerability is fixed in 3.1.0.
@node-oauth/oauth2-server is a module for implementing an OAuth2 server in Node.js. The token exchange path accepts RFC7636-invalid code_verifier values (including one-character strings) for S256 PKCE flows. Because short/weak verifiers are accepted and failed verifier attempts do not consume the authorization code, an attacker who intercepts an authorization code can brute-force code_verifier guesses online until token issuance succeeds.
CVE-2026-41679 is a critical improper authentication vulnerability in Paperclip, a Node.js server and React UI platform for orchestrating AI agents. Prior to version 2026.416.0, an unauthenticated attacker can remotely execute arbitrary code on any network-accessible Paperclip instance running in authenticated mode with default configuration. The attack requires no user interaction or credentials and involves a chain of six API calls. The vulnerability is patched in version 2026.416.0.
A path traversal vulnerability exists in the MCPHub MCPB file upload handler due to improper sanitization of the 'name' field in the uploaded manifest.json. The 'name' field is directly concatenated into file system paths without validation, allowing an attacker to craft a malicious MCPB file that causes extraction and file operations outside the intended directory. This can lead to arbitrary file creation or deletion on the server file system.
Craft CMS versions 4.x through 4.17.8 and 5.x through 5.9.14 contain a Server-Side Request Forgery (SSRF) vulnerability in the resource-js endpoint. This vulnerability arises when the trustedHosts configuration is not explicitly restricted, allowing the application to trust a client-supplied Host header. An attacker can exploit this to control the baseUrl used in prefix validation, causing the server to make arbitrary HTTP requests. Versions 4.
CVE-2026-41304 is a command injection vulnerability in WWBN AVideo versions 29.0 and below. The vulnerability exists in the CloneSite plugin's cloneServer.json.php endpoint, where user input from the 'url' parameter is unsafely concatenated into a shell command executed via exec(). This allows an attacker to inject arbitrary shell commands, leading to remote code execution on the server. A fix for this issue is included in commit 473c609fc2defdea8b937b00e86ce88eba1f15bb.
CVE-2026-40911 is a critical code injection vulnerability in WWBN AVideo versions 29.0 and earlier. The YPTSocket plugin's WebSocket server relays attacker-controlled JSON message fields without sanitization, which are then passed to eval() calls on connected clients. This allows an unauthenticated attacker to execute arbitrary JavaScript in the context of all connected users, including administrators. The vulnerability enables universal account takeover, session theft, and execution of privileged actions. A fix is available in commit c08694bf6264eb4decceb78c711baee2609b4efd.
mailcow: dockerized is an open source groupware/email suite based on docker. In versions prior to 2026-03b, the user dashboard's "Seen successful connections" (login history) renders the client IP from login logs without HTML escaping. Because the server trusts the X-Real-IP header as the source IP for logging, an attacker can inject HTML/JS into this field. This Self-XSS can be exploited by a Login CSRF to force the victim into the attacker's account, and then read emails in a previous browser tab. Version 2026-03b fixes the vulnerability.
Nest is a framework for building scalable Node.js server-side applications. Prior to 11.1.19, when an attacker sends many small, valid JSON messages in one TCP frame, handleData() recurses once per message; the buffer shrinks each call.maxBufferSize is never reached; call stack overflows instead. A ~47 KB payload is sufficient to trigger RangeError. This vulnerability is fixed in 11.1.19.
Next AI Draw.io is a next.js web application that integrates AI capabilities with draw.io diagrams. Prior to 0.4.15, the embedded HTTP sidecar contains three POST handlers (/api/state, /api/restore, and /api/history-svg) that process incoming requests by accumulating the entire request body into a JavaScript string without any size limitations. Node.js buffers the entire payload in the V8 heap. Sending a sufficiently large body (e.g., 500 MiB or more) will exhaust the process heap memory, leading to an Out-of-Memory (OOM) error that crashes the MCP server. This vulnerability is fixed in 0.4.15.
SignalK Server versions prior to 2.25.0 are vulnerable to an unauthenticated Regular Expression Denial of Service (ReDoS) attack. The vulnerability arises from the WebSocket subscription handling logic where unescaped regex metacharacters in the 'context' parameter can trigger catastrophic backtracking in the Node.js event loop. This causes the server CPU to spike to 100%, resulting in a complete denial of service. The issue is fixed in version 2.25.0.
A flaw has been found in langgenius dify up to 1.13.3. This issue affects the function parse_openai_plugin_json_to_tool_bundle of the file api/core/tools/utils/parser.py of the component ApiBasedToolSchemaParser. Executing a manipulation of the argument url can lead to server-side request forgery. The attack can be launched remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
CVE-2026-5131 is a Server-Side Request Forgery (SSRF) vulnerability in Nomios Poland's GREENmod product. The issue arises from incorrectly configured access control lists on named pipes used for communication between plugins, the web portal, and the system service. This misconfiguration allows an attacker to upload arbitrary XML or JSON files to the named pipe, which are then processed with the privileges of the service user. Exploitation enables SSRF to any Windows system running the vulnerable agent that supports SMB or WebDav communication. The vulnerability has a CVSS 4.0 base score of 6.9 (medium severity). It was fixed in version 2.8.33 of GREENmod.
SiYuan is an open-source personal knowledge management system. In versions 3.6.3 and prior, the /api/av/removeUnusedAttributeView endpoint constructs a filesystem path using the user-controlled id parameter without validation or path boundary enforcement. An attacker can inject path traversal sequences such as ../ into the id value to escape the intended directory and delete arbitrary .json files on the server, including global configuration files and workspace metadata. This issue has been fixed in version 3.6.4.