Technical impact
The vulnerability in DBHub allows attackers to bypass the read-only mode by injecting backslash-escaped quotes into SQL strings. The parser misinterprets these escaped sequences during the scanSingleQuotedString operation, enabling the execution of write or DDL statements that should be prohibited. As a result, unauthorized modifications, deletions, or schema changes can occur against MySQL, MariaDB, or PostgreSQL data, compromising the integrity of the database. This flaw is classified as CWE-436, which denotes improper escaping of characters.
Affected Systems
Bytebase DBHub versions prior to 1.7.0 are affected. The issue has been observed in release 1.6.1 and earlier built for MySQL, MariaDB, and PostgreSQL connections. Users of these older releases are at risk if their MCP clients are allowed to issue execute_sql commands while configured for read-only access.
Risk and Exploitability
The CVSS score of 7.2 indicates a moderate to high severity. EPSS information is not available, so the likelihood of exploitation cannot be quantified. The vulnerability is not listed in CISA KEV. Attackers must possess the ability to run SQL via an MCP client; the likely entry point is the execute_sql command, which, when combined with the bypass, enables executing additional statements disguised within string literals. Because the flaw manipulates the parsing of quoted strings, it can be triggered without elevated privileges on the database itself, providing a path for data tampering or loss.