Database modification via retained report credentials
Published Nov 10, 2025 · Updated Nov 10, 2025
Improper privilege management in Google Data Studio before 2025-07-21 allows remote authenticated users to execute arbitrary SQL. When a viewer copies a JDBC-backed report, the copied data source retains the owner's stored database credentials and accepts attacker-controlled statements through Custom Query. Report view access is sufficient; the statements run with the owner's database rights and can read, insert, or delete connected database data.
Summary
What happened
Improper privilege management in Google Data Studio before 2025-07-21 allows remote authenticated users to execute arbitrary SQL. When a viewer copies a JDBC-backed report, the copied data source retains the owner's stored database credentials and accepts attacker-controlled statements through Custom Query. Report view access is sufficient; the statements run with the owner's database rights and can read, insert, or delete connected database data.
The record
- CVE
- CVE-2025-12405
- Published
- Nov 10, 2025
- Updated
- Nov 10, 2025
- Vendor
- Go standard library
- Product
- Data Studio
- Classifications
- CWE-269, CAPEC-122, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 10, 2025CVE publishedPublication date reported by the CVE source.
- Nov 10, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2025-07-21
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Report-copy Custom Query proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo