{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-38510 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-38510 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-38510 is a high-severity missing authorization vulnerability in tolgee-platform, published on 27 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-38510 and fix it if it is affected.\n\nWhat it is: CVE-2023-38510 is a high-severity missing authorization vulnerability in tolgee-platform, published on 27 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-38510 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-2023-38510/ (Markdown: https://insights.sbomify.com/CVE-2023-38510/index.md)","id":"CVE-2023-38510","markdown":"https://insights.sbomify.com/CVE-2023-38510/index.md","name":"CVE-2023-38510","record":{"aliases":["GHSA-4f9j-4vh4-p85v"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Localization platform","requires_auth":"low_privilege","summary":"Attackers with exposed API keys can bypass permission checks on certain endpoints, potentially accessing unauthorized data in Tolgee localization projects.","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":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Tolgee is an open-source localization platform. Starting in version 3.14.0 and prior to version 3.23.1, when a request is made using an API key, the backend fails to verify the permission scopes associated with the key, effectively bypassing permission checks entirely for some endpoints. It's important to note that this vulnerability only affects projects that have inadvertently exposed their API keys on the internet. Projects that have kept their API keys secure are not impacted. This issue is fixed in version 3.23.1.","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 Lacks Permission Check for API Key for some endpoints","id":"CVE-2023-38510","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"iTop Dashboard editor vulnerable dashboard config file parameter","id":"CVE-2023-38511"},"packages":[],"prev":{"headline":"XWiki Platform's obfuscated email addresses should not be sorted","id":"CVE-2023-38509"},"products":["tolgee-platform"],"published":"2023-07-27","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":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"},{"cvss_score":2.7,"headline":"Tolgee's API key scopes not checked when querying translation data","id":"CVE-2024-32466","kev_date_added":null,"published":"2024-04-18"}],"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":"total"},"state":"PUBLISHED","updated":"2024-10-03","vendors":["tolgee"]},"summary":"Attackers with exposed API keys can bypass permission checks on certain endpoints, potentially accessing unauthorized data in Tolgee localization projects.","url":"https://insights.sbomify.com/CVE-2023-38510/"}