CVE-2025-12743: SQL Injection in Looker Project Generation Endpoint Allows Access to Internal MySQL Database
The Looker endpoint for generating new projects from database connections allows users to specify "looker" as a connection name, which is a reserved internal name for Looker's internal MySQL database. The schemas parameter is vulnerable to SQL injection, enabling attackers to manipulate SELECT queries that are constructed and executed against the internal MySQL database. This vulnerability allows users with developer permissions to extract data from Looker's internal MySQL database.
Looker-hosted and Self-hosted were found to be vulnerable. This issue has already been mitigated for Looker-hosted instances. No user action is required for these.
Self-hosted instances must be upgraded as soon as possible. This vulnerability has been patched in all supported versions of Self-hosted. The versions below have all been updated to protect against this vulnerability. You can download these versions at the Looker download page https://download.looker.com/ : 24.12.106 24.18.198+ 25.0.75 25.6.63+ 25.8.45+ 25.10.33+ 25.12.1+ 25.14+
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-12743?
CVE-2025-12743 is classified as a critical severity vulnerability due to its potential to allow SQL injection attacks.
How do I fix CVE-2025-12743?
To fix CVE-2025-12743, it is recommended to update to the latest version of Looker where the vulnerability has been addressed.
Who is affected by CVE-2025-12743?
CVE-2025-12743 affects all supported versions of Looker that allow specification of 'looker' as a connection name.
What can an attacker achieve with CVE-2025-12743?
An attacker exploiting CVE-2025-12743 can conduct SQL injection attacks which may lead to unauthorized access to Looker's internal MySQL database.
Is there a workaround for CVE-2025-12743?
As of now, the best course of action for CVE-2025-12743 is to apply the recommended security patches and updates provided by Looker.