A high-severity authorization flaw in Coze Studio versions 0.5.1 and earlier permits authenticated users to execute unauthorized SQL queries against other workspaces, risking significant data exposure.

The vulnerability is an authorization bypass (CWE-863) stemming from a failure to validate that table names specified in workflow SQL customization nodes belong to the caller's authorized workspace. An authenticated attacker can exploit this by enumerating predictable table identifiers to read, insert, or delete data within other workspaces' memory databases.

The ability to perform unauthorized cross-tenant database operations poses a critical risk to data confidentiality, integrity, and availability. By manipulating SQL queries against arbitrary workspaces, an attacker could exfiltrate sensitive information, inject malicious data, or cause service disruption. Given the CVSS score of 8.8, this vulnerability represents a significant threat to multi-tenant environments where strict data isolation is a primary security requirement.

Immediate Action: There is currently no official patch available for this vulnerability. Organizations should restrict access to workflow creation capabilities to trusted users and monitor for unauthorized database interaction patterns.

Proactive Monitoring: Security teams should review application logs for anomalous SQL execution patterns, specifically monitoring for cross-workspace identifier access or unexpected INSERT, DELETE, or SELECT queries originating from workflow nodes.

Compensating Controls: Deploy a Web Application Firewall (WAF) to inspect and filter suspicious SQL payloads in incoming requests, and implement internal database-level access controls that strictly enforce tenant isolation.

Public Exploit Available: Unknown

This vulnerability presents a substantial risk to data privacy in multi-tenant Coze Studio deployments. Administrators are urged to prioritize the implementation of compensating controls, such as enhanced logging and strict user privilege management, while awaiting a formal vendor patch. Constant vigilance is required until a definitive fix is applied to remediate the underlying authorization failure.