{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-32466 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-32466 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-32466 is a low-severity missing authorization vulnerability in tolgee-platform, published on 18 Apr 2024. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-32466 and fix it if it is affected.\n\nWhat it is: CVE-2024-32466 is a low-severity missing authorization vulnerability in tolgee-platform, published on 18 Apr 2024. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-32466 in the wild and no public exploit code.\n\nAffected product: tolgee-platform. 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-2024-32466/ (Markdown: https://insights.sbomify.com/CVE-2024-32466/index.md)","id":"CVE-2024-32466","markdown":"https://insights.sbomify.com/CVE-2024-32466/index.md","name":"CVE-2024-32466","record":{"aliases":["GHSA-r95p-fqqv-fppc"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Tolgee localization platform","requires_auth":"high_privilege","summary":"Attackers with valid API keys lacking translation.view scope can read translation data due to missing authorization checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"tolgee","vendor":"tolgee"}],"cvss":{"score":2.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Tolgee is an open-source localization platform. For the `/v2/projects/translations` and `/v2/projects/{projectId}/translations` endpoints, translation data was returned even when API key was missing `translation.view` scope. However, it was impossible to fetch the data when user was missing this scope. So this is only relevant for API keys generated by users permitted to `translation.view`. This vulnerability is fixed in v3.57.2","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":"Tolgee's API key scopes not checked when querying translation data","id":"CVE-2024-32466","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Meteraphsere vulnerable to unauthorized viewing by workspace members","id":"CVE-2024-32467"},"packages":[],"prev":{"headline":"Git's protections for cloning untrusted repositories can be bypassed","id":"CVE-2024-32465"},"products":["tolgee-platform"],"published":"2024-04-18","related":[{"cvss_score":9.8,"headline":"Tolgee's configuration all configuration properties leaked in public configuration DTO","id":"CVE-2024-52297","kev_date_added":null,"published":"2024-11-12"},{"cvss_score":9.3,"headline":"Tolgee has an XXE Injection in Translation Import","id":"CVE-2026-32251","kev_date_added":null,"published":"2026-03-12"},{"cvss_score":8.1,"headline":"Tolgee Lacks Permission Check for API Key for some endpoints","id":"CVE-2023-38510","kev_date_added":null,"published":"2023-07-27"},{"cvss_score":6.5,"headline":"Tolgee' API keys created by server admin users bypass the permission check","id":"CVE-2024-32470","kev_date_added":null,"published":"2024-04-18"},{"cvss_score":5.5,"headline":"HTML Injection with email in Tolgee","id":"CVE-2023-41316","kev_date_added":null,"published":"2023-09-07"}],"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":"2024-08-02","vendors":["tolgee"]},"summary":"Attackers with valid API keys lacking translation.view scope can read translation data due to missing authorization checks.","url":"https://insights.sbomify.com/CVE-2024-32466/"}