dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-12397

HIGH · 7.6 CVSS v4.0 Published 2025-11-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in Looker Studio where authenticated users with report view access could inject malicious SQL queries targeting BigQuery data sources. The injected SQL executes with the elevated permissions of the report owner, enabling unauthorized data access.

MitigationVendor has patched this vulnerability; no customer action required. Organizations should review access audit logs for any suspicious SQL patterns during the vulnerable period and ensure least-privilege principles are applied to report sharing configurations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:Clear

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate Looker Studio audit logs in Google Cloud
    In Google Cloud Console, navigate to Logging > Logs Explorer and filter for logName containing 'data-studio' or 'looker-studio'. Look for entries with 'bigquery.jobs.create' or SQL-related operations.
    Affected if Unusual SQL patterns, unexpected data source queries, or queries targeting sensitive BigQuery tables appear in logs from the vulnerable period.
  2. Review BigQuery audit logs for suspicious query patterns
    In BigQuery > Audit Logs, examine job logs for the vulnerable period. Filter for queries containing UNION statements, comment markers (--, /* */), or unexpected table references.
    Affected if Queries executed with elevated permissions (report owner credentials) contain injected SQL syntax that differs from legitimate Looker Studio-generated queries.
  3. Identify reports with sensitive BigQuery data sources
    In Looker Studio, review all owned reports. Check each report's data source configuration to identify which BigQuery projects/datasets they connect to and confirm the owner credentials used.
    Affected if Reports using BigQuery data sources with access to sensitive datasets were shared with users who only have view permissions.
  4. Check report sharing configurations for over-privileged access
    In Looker Studio, open each report > Share settings. Identify reports where 'View' access was granted to users outside the report owner's organization, particularly to external accounts.
    Affected if Reports with BigQuery data sources were shared with viewers outside the organization, allowing the SQL injection to execute with owner permissions on external accounts.
  5. Correlate user activity with data access anomalies
    Cross-reference Looker Studio access logs with BigQuery job logs. Identify viewer accounts that executed queries with permissions different from their own role.
    Affected if View-only users appear to have run BigQuery queries that accessed data beyond their standard permissions, indicating potential exploitation.

Your environment is affected if Looker Studio reports with access to sensitive BigQuery data sources were shared with viewers during the vulnerable period and audit logs show SQL injection patterns or unauthorized data access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Vendor has patched this vulnerability; no customer action required. Organizations should review access audit logs for any suspicious SQL patterns during the vulnerable period and ensure least-privilege principles are applied to report sharing configurations.

Recommended fix High confidence
  1. No action required. Google has patched this vulnerability server-side as of 21 July 2025. Looker Studio users do not need to take any manual steps.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12397 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12397 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data