The SQL Chat application is vulnerable to unauthenticated server-side request forgery and remote command execution, posing a significant risk to internal database infrastructure.

The application exposes four unauthenticated API endpoints, specifically within the connection testing and query execution modules, which accept user-supplied database connection strings and execute arbitrary SQL statements. This flaw constitutes a severe server-side request forgery (SSRF) vulnerability that allows unauthenticated attackers to interact with internal resources.

A successful exploit allows unauthorized actors to bypass network perimeters and interact directly with internal database systems. This could lead to full data exfiltration, unauthorized schema modification, or the use of the server as a pivot point to conduct further attacks on the internal network. Given the CVSS score of 8.7, this vulnerability represents a high-severity threat to data confidentiality and integrity.

Immediate Action: Restrict access to the affected API endpoints at the network level until an official vendor patch is released and applied.

Proactive Monitoring: Review web server and application logs for unusual POST requests directed at /api/connection/ paths, specifically monitoring for anomalous database connection attempts or unexpected query patterns.

Compensating Controls: Implement a Web Application Firewall (WAF) rule to block or inspect incoming traffic to the SQL Chat API endpoints, specifically looking for requests that contain suspicious database connection parameters.

Public Exploit Available: Unknown

The exposure of unauthenticated database execution endpoints is a critical security failure that demands immediate administrative attention. Administrators should treat the affected instances as compromised until they can be isolated from untrusted networks and updated with security fixes. Ensure that these services are never exposed to the public internet without strict authentication and network-level access controls.