dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2025-12405

HIGH · 7.7 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 →
83/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
An improper privilege management vulnerability was found in Looker Studio. It impacted all JDBC-based connectors. A Looker Studio user with report view access could make a copy of the report and execute arbitrary SQL that would run on the data source database due to the stored credentials attached to the report. 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

This was an improper privilege management vulnerability in Looker Studio's JDBC connectors where a user with only report VIEW access could make a copy of the report, inheriting the stored database credentials and thereby gaining the ability to execute arbitrary SQL on the underlying data source database.

MitigationNo customer action required - Google patched this vulnerability server-side on 21 July 2025. Organizations may wish to audit Looker Studio access logs around that date for any suspicious report copying activity.

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:H/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. Identify Looker Studio reports with JDBC data sources
    Review your Looker Studio reports and identify any that use JDBC connectors to connect to external databases (MySQL, PostgreSQL, Oracle, SQL Server, etc.). Check report settings or data source configurations for JDBC connection details.
    Affected if Reports exist that use JDBC connectors to connect to external databases
  2. Audit user permission levels on reports
    Review the permission settings on identified JDBC-connected reports. Document which users have only VIEW access versus EDITOR or OWNER access levels.
    Affected if There are users with only VIEW access to reports that use JDBC data sources
  3. Search access logs for report copy operations by viewers
    Export or query Looker Studio audit/access logs for the period around July 21, 2025 (and after). Look for 'createCopy' or 'copyReport' actions performed by users who only have VIEW permission on the source report.
    Affected if Logs show report copy operations performed by users who only had VIEW access
  4. Check for unexpected SQL query execution
    Review database audit logs or Looker Studio query logs for any SQL queries executed from Looker Studio that originate from users who should only have had VIEW access to the underlying reports.
    Affected if SQL queries were executed by users who only had VIEW access to the source reports

A user is affected if they have Looker Studio reports with JDBC data sources and audit logs reveal that users with only VIEW permission successfully copied reports or executed SQL queries after July 21, 2025.

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 this vulnerability server-side on 21 July 2025. Organizations may wish to audit Looker Studio access logs around that date for any suspicious report copying activity.

Recommended fix High confidence
  1. No action required. This vulnerability was patched by Google on 21 July 2025.
  2. The patch was applied server-side to Looker Studio's JDBC-based connectors.
  3. Verify that your Looker Studio reports are running on the current (post-July 2025) platform version by checking the Looker Studio help documentation or contacting Google Cloud support if you have concerns.

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-12405 — 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-12405 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