# CVE-2025-12397: SQL Injection in Looker Studio

> A user with report view access could inject SQL to execute commands with the report owner's permissions in Looker Studio reports using BigQuery.

- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N/U:Clear`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Nov 2025
- **Updated:** 10 Nov 2025
- **Also known as:** GHSA-qmv7-fcxw-pj9w

## What is CVE-2025-12397?

CVE-2025-12397 is a high-severity SQL injection vulnerability in Google Cloud Looker Studio, published on 10 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A SQL injection vulnerability was found in Looker Studio.

A Looker Studio user with report view access could inject malicious SQL that would execute with the report owner's permissions. The vulnerability affected to reports with BigQuery as the data source.

This vulnerability was patched on 21 July 2025, and no customer action is needed.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2025-12397?


## How do I fix CVE-2025-12397?

No fix has been published for CVE-2025-12397 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-12397 being exploited?

There is no known exploitation of CVE-2025-12397 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-12397 and fix it if it is affected.

What it is: CVE-2025-12397 is a high-severity SQL injection vulnerability in Google Cloud Looker Studio, published on 10 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-12397 in the wild and no public exploit code.

Affected product: Google Cloud Looker Studio. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-12397/ (Markdown: https://insights.sbomify.com/CVE-2025-12397/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-12397
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-12397
- OSV: https://osv.dev/vulnerability/CVE-2025-12397

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-12397/
Summaries are generated and may contain mistakes; the official description above is the record.