SQL Injection in Looker Studio
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Google Cloud | Looker Studio | unaffected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Cloud Looker | — | |
| Looker | — |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.269% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Google
Google cloud Looker Google looker |
|
| Vendors & Products |
Google
Google cloud Looker Google looker |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A SQL injection vulnerability was discovered in Looker Studio that allowed for data exfiltration from BigQuery data sources. By creating a malicious report with native functions enabled, and having the victim access the report, an attacker could execute injected SQL queries with the victim's permissions in BigQuery. This vulnerability was patched on 07 July 2025, and no customer action is needed. | |
| Title | SQL Injection in Looker Studio | |
| Weaknesses | CWE-89 | |
| References |
| |
| Metrics |
cvssV4_0
|