Next Ai Draw Io
Monthly
Server-side request forgery in Next AI Draw.io through 0.4.16 enables unauthenticated remote attackers to reach arbitrary internal HTTP services by exploiting a hostname validation bypass in the POST /api/parse-url endpoint. The validator inspects hostnames as string patterns only - without DNS resolution - allowing attackers to supply hostnames that pass the string check yet resolve to internal addresses, including cloud metadata endpoints such as the AWS IMDSv1 service. A publicly available proof-of-concept exists per VulnCheck; no CISA KEV listing has been identified at time of analysis.
Reflected XSS in Next AI Draw.io 0.2.1 through 0.4.16 allows unauthenticated remote attackers to inject and execute arbitrary JavaScript in the localhost origin by crafting malicious URLs containing a payload in the unsanitized `mcp` query parameter. Successful exploitation - which requires a victim to click the crafted link - enables theft of diagram session tokens and API credentials accessible within that browser origin. Publicly available exploit code exists (GitHub issue #917 via VulnCheck), though no CISA KEV listing confirms active exploitation at time of analysis.
Server-side request forgery in Next AI Draw.io through 0.4.16 enables unauthenticated remote attackers to reach arbitrary internal HTTP services by exploiting a hostname validation bypass in the POST /api/parse-url endpoint. The validator inspects hostnames as string patterns only - without DNS resolution - allowing attackers to supply hostnames that pass the string check yet resolve to internal addresses, including cloud metadata endpoints such as the AWS IMDSv1 service. A publicly available proof-of-concept exists per VulnCheck; no CISA KEV listing has been identified at time of analysis.
Reflected XSS in Next AI Draw.io 0.2.1 through 0.4.16 allows unauthenticated remote attackers to inject and execute arbitrary JavaScript in the localhost origin by crafting malicious URLs containing a payload in the unsanitized `mcp` query parameter. Successful exploitation - which requires a victim to click the crafted link - enables theft of diagram session tokens and API credentials accessible within that browser origin. Publicly available exploit code exists (GitHub issue #917 via VulnCheck), though no CISA KEV listing confirms active exploitation at time of analysis.