{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-23628 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-23628 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-23628 is a medium-severity vulnerability in metabase, published on 28 Jan 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-23628 and fix it if it is affected.\n\nWhat it is: CVE-2023-23628 is a medium-severity vulnerability in metabase, published on 28 Jan 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-23628 in the wild and no public exploit code.\n\nAffected product: metabase. 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-2023-23628/ (Markdown: https://insights.sbomify.com/CVE-2023-23628/index.md)","id":"CVE-2023-23628","markdown":"https://insights.sbomify.com/CVE-2023-23628/index.md","name":"CVE-2023-23628","record":{"aliases":["GHSA-492f-qxr3-9rrv"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Metabase analytics platform","requires_auth":"low_privilege","summary":"Sandboxed users can view recipient lists for dashboard subscriptions, exposing sensitive user information to unauthorized actors.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"metabase","vendor":"metabase"}],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Metabase is an open source data analytics platform. Affected versions are subject to Exposure of Sensitive Information to an Unauthorized Actor. Sandboxed users shouldn't be able to view data about other Metabase users anywhere in the Metabase application. However, when a sandbox user views the settings for a dashboard subscription, and another user has added users to that subscription, the sandboxed user is able to view the list of recipients for that subscription. This issue is patched in versions 0.43.7.1, 1.43.7.1, 0.44.6.1, 1.44.6.1, 0.45.2.1, and 1.45.2.1. There are no workarounds.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Metabase subject to Exposure of Sensitive Information to an Unauthorized Actor","id":"CVE-2023-23628","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Metabase subject to Improper Privilege Management","id":"CVE-2023-23629"},"packages":[],"prev":{"headline":"Sanitize vulnerable to Cross-site Scripting via Improper neutralization of `noscript` element","id":"CVE-2023-23627"},"products":["metabase"],"published":"2023-01-28","related":[{"cvss_score":10,"headline":"Metabase SQL Injection","id":"CVE-2026-72898","kev_date_added":"2026-08-11","published":"2026-08-10"},{"cvss_score":10,"headline":"Metabase GeoJSON API Local File Inclusion","id":"CVE-2021-41277","kev_date_added":"2024-11-12","published":"2021-11-17"},{"cvss_score":10,"headline":"Metabase: Remote Code Execution via Snowflake JDBC Driver Arbitrary File Write","id":"CVE-2026-50148","kev_date_added":null,"published":"2026-07-15"},{"cvss_score":10,"headline":"Metabase vulnerable to remote code execution via POST /api/setup/validate API endpoint","id":"CVE-2023-37470","kev_date_added":null,"published":"2023-08-04"},{"cvss_score":9.9,"headline":"Metabase: Unsafe Deserialization of H2 Query Results","id":"CVE-2026-59827","kev_date_added":null,"published":"2026-07-09"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2023-38646","kev_date_added":null,"published":"2023-07-21"},{"cvss_score":9.1,"headline":"Metabase: Arbitrary Code Execution via Database Connection Detail Bypass","id":"CVE-2026-59826","kev_date_added":null,"published":"2026-07-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-03-10","vendors":["metabase"]},"summary":"Sandboxed users can view recipient lists for dashboard subscriptions, exposing sensitive user information to unauthorized actors.","url":"https://insights.sbomify.com/CVE-2023-23628/"}