Search Results (7 CVEs found)

CVE Vendors Products Updated CVSS v3.1
CVE-2026-73037 1 Dayuanjiang 1 Next-ai-draw-io 2026-08-13 6.1 Medium
Next AI Draw.io 0.2.1 through 0.4.16 contains a reflected cross-site scripting vulnerability in the mcp query parameter that is interpolated without escaping into HTML and JavaScript. Attackers can craft malicious URLs to execute arbitrary JavaScript in the localhost origin, enabling exfiltration of diagram sessions and API data.
CVE-2026-72777 1 Dayuanjiang 1 Next-ai-draw-io 2026-08-13 8.6 High
Next AI Draw.io through 0.4.16 contains a server-side request forgery vulnerability in the POST /api/parse-url endpoint due to hostname validation that only checks string patterns without DNS resolution. Unauthenticated attackers can supply hostnames that bypass string validation but resolve to internal addresses, allowing them to reach arbitrary internal HTTP services and exfiltrate responses including cloud metadata.
CVE-2026-50755 1 Dayuanjiang 1 Next-ai-draw-io 2026-08-04 9.8 Critical
An issue in DayuanJiang next-ai-draw-io 0.4.13 allows a remote attacker to obtain sensitive information via the X-Forwarded-For header value
CVE-2026-50756 1 Dayuanjiang 1 Next-ai-draw-io 2026-08-04 7.5 High
An issue in DayuanJiang next-ai-draw-io 0.4.13 allows a remote attacker to obtain sensitive information via the x-ai-provider component
CVE-2026-50757 1 Dayuanjiang 1 Next-ai-draw-io 2026-08-03 7.8 High
Directory Traversal vulnerability in DayuanJiang next-ai-draw-io 0.4.13 allowsa remote attacker to execute arbitrary code via the nex-ai-draw-io/mcp-server
CVE-2026-50758 1 Dayuanjiang 1 Next-ai-draw-io 2026-08-03 8.1 High
Cross Site Scripting vulnerability in DayuanJiang next-ai-draw-io 0.4.13 allows a remote attacker to execute arbitrary code via the mcp parameter
CVE-2026-40608 1 Dayuanjiang 2 Next-ai-draw-io, Next Ai Draw.io 2026-04-27 6.2 Medium
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.