| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Looker Studio. It has been classified as critical. This issue affects some unknown processing. Performing a manipulation results in sql injection. This vulnerability is known as CVE-2025-12409. Remote exploitation of the attack is possible. No exploit is available. This product is a managed service, so users do not have direct control over vulnerability countermeasures. Upgrading the affected component is recommended.
Details
A vulnerability was found in Google Looker Studio. It has been classified as critical. This affects an unknown code block. The manipulation with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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.
The weakness was published by Liv Matan as gcp-2025-053. The advisory is shared at cloud.google.com. This vulnerability is uniquely identified as CVE-2025-12409 since 10/28/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 11/10/2025). MITRE ATT&CK project uses the attack technique T1505 for this issue.
Upgrading to version 2025-07-07 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-44038). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
License
Managed Service
- yes
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Status: 🔍0-Day Time: 🔒
Upgrade: Looker Studio 2025-07-07
Timeline
07/07/2025 Countermeasure disclosed10/28/2025 CVE reserved
11/10/2025 Advisory disclosed
11/10/2025 VulDB entry created
11/10/2025 VulDB entry last update
Sources
Vendor: google.comAdvisory: gcp-2025-053
Researcher: Liv Matan
Status: Confirmed
CVE: CVE-2025-12409 (🔒)
GCVE (CVE): GCVE-0-2025-12409
GCVE (VulDB): GCVE-100-331665
EUVD: 🔒
Entry
Created: 11/10/2025 11:55Updated: 11/10/2025 12:04
Changes: 11/10/2025 11:55 (70), 11/10/2025 12:04 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.