dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-12409

HIGH · 7.3 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 →
77/100
Remediation priority · High
Remotely reachable

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 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.

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 enabling data exfiltration from BigQuery. Attackers create malicious reports with native functions enabled; when victims access these reports, injected SQL queries execute with the victim's BigQuery permissions, allowing unauthorized data access.

MitigationNo customer action required; Google patched the vulnerability server-side on 07 July 2025. Verify Looker Studio access controls and report sharing settings to limit exposure to similar attacks.

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
A
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/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. Confirm Looker Studio usage
    Inventory all Looker Studio reports and dashboards in use within the organization through the Looker Studio admin console or by querying connected data sources.
    Affected if Looker Studio is actively used and connected to BigQuery datasets.
  2. Identify reports with native functions enabled
    Review Looker Studio report settings to identify which reports have 'native functions' or 'native query' features enabled, as this feature allows direct SQL execution against BigQuery.
    Affected if Reports have native functions enabled, which is the attack vector described in the CVE.
  3. Audit report sharing and access controls
    Examine sharing settings on all Looker Studio reports to determine which reports are shared broadly or accessible to external users, particularly reports created before July 2025.
    Affected if Reports with native functions enabled are shared widely or with untrusted users.
  4. Review BigQuery access logs for unauthorized queries
    Analyze BigQuery audit logs for SQL queries executed under user credentials that originated from Looker Studio reports, looking for unusual data access patterns or queries to sensitive datasets.
    Affected if Unexpected or unauthorized BigQuery queries appear in audit logs originating from Looker Studio report access.
  5. Check for pre-patch report creations
    Identify Looker Studio reports created or modified before July 7, 2025 (the patch date), as these could contain malicious payloads injected prior to remediation.
    Affected if Reports with native functions enabled were created or modified before July 2025.

A user is affected if Looker Studio reports with native functions enabled were accessed by victims, resulting in unauthorized BigQuery data access, particularly for reports created or shared before the July 2025 server-side patch.

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

No customer action required; Google patched the vulnerability server-side on 07 July 2025. Verify Looker Studio access controls and report sharing settings to limit exposure to similar attacks.

Recommended fix High confidence
  1. No customer action required. Google has already patched this vulnerability in Looker Studio as of July 7, 2025. The fix was applied server-side and requires no user intervention.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12409 — 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-12409 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