{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-12743 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-12743 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-12743 is a medium-severity SQL injection vulnerability in Google Cloud Looker, published on 19 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-12743 and fix it if it is affected.\n\nWhat it is: CVE-2025-12743 is a medium-severity SQL injection vulnerability in Google Cloud Looker, published on 19 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-12743 in the wild and no public exploit code.\n\nAffected product: Google Cloud Looker. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-12743/ (Markdown: https://insights.sbomify.com/CVE-2025-12743/index.md)","id":"CVE-2025-12743","markdown":"https://insights.sbomify.com/CVE-2025-12743/index.md","name":"CVE-2025-12743","record":{"aliases":["GHSA-8fvv-8rcf-99j8"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Looker BI platform","requires_auth":"low_privilege","summary":"Attackers with developer permissions can extract data from Looker's internal MySQL database via SQL injection in the project generation endpoint.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GoogleCloud","cpe":[],"cvss":{"score":6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/U:Red","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"The Looker endpoint for generating new projects from database connections allows users to specify \"looker\" as a connection name, which is a reserved internal name for Looker's internal MySQL database. The schemas parameter is vulnerable to SQL injection, enabling attackers to manipulate SELECT queries that are constructed and executed against the internal MySQL database. This vulnerability allows users with developer permissions to extract data from Looker's internal MySQL database.\n\nLooker-hosted and Self-hosted were found to be vulnerable.\nThis issue has already been mitigated for Looker-hosted instances. No user action is required for these.\n\nSelf-hosted instances must be upgraded as soon as possible. This vulnerability has been patched in all supported versions of Self-hosted.\nThe versions below have all been updated to protect against this vulnerability. You can download these versions at the Looker download page  https://download.looker.com/ :\n  *  24.12.106\n  *  24.18.198+\n  *  25.0.75\n  *  25.6.63+\n  *  25.8.45+\n  *  25.10.33+\n  *  25.12.1+\n  *  25.14+","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"SQL Injection in Looker Project Generation Endpoint Allows Access to Internal MySQL Database","id":"CVE-2025-12743","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Abrt: command-injection in abrt leading to local privilege escalation","id":"CVE-2025-12744"},"packages":[],"prev":{"headline":"Remote Code Execution in Looker via Teradata JDBC Driver","id":"CVE-2025-12742"},"products":["Looker"],"published":"2025-11-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-19","vendors":["Google Cloud"]},"summary":"Attackers with developer permissions can extract data from Looker's internal MySQL database via SQL injection in the project generation endpoint.","url":"https://insights.sbomify.com/CVE-2025-12743/"}