{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-50265 exists.","fix":"No fix has been published for CVE-2023-50265 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-50265 is a high-severity path traversal vulnerability in morpheus65535 bazarr, published on 15 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-50265 and fix it if it is affected.\n\nWhat it is: CVE-2023-50265 is a high-severity path traversal vulnerability in morpheus65535 bazarr, published on 15 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-50265 exists.\n\nAffected product: morpheus65535 bazarr. 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-50265/ (Markdown: https://insights.sbomify.com/CVE-2023-50265/index.md)","id":"CVE-2023-50265","markdown":"https://insights.sbomify.com/CVE-2023-50265/index.md","name":"CVE-2023-50265","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Bazarr subtitle manager","requires_auth":"none","summary":"An attacker can read arbitrary files from the server via the /api/swaggerui/static endpoint due to lack of filename validation.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"bazarr","vendor":"bazarr"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Bazarr manages and downloads subtitles. Prior to 1.3.1, the /api/swaggerui/static endpoint in bazarr/app/ui.py does not validate the user-controlled filename variable and uses it in the send_file function, which leads to an arbitrary file read on the system. This issue is fixed in version 1.3.1.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Bazarr Arbitrary file read in /api/swaggerui/static endpoint","id":"CVE-2023-50265","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"Bazarr Blind Server-Side Request Forgery (SSRF) in the /test/\u003cprotocol\u003e/ endpoint","id":"CVE-2023-50266"},"packages":[],"prev":{"headline":"Bazarr Arbitrary file read in /system/backup/download/ endpoint","id":"CVE-2023-50264"},"products":["bazarr"],"published":"2023-12-15","related":[{"cvss_score":8.2,"headline":"Path traversal in n/a","id":"CVE-2024-40348","kev_date_added":null,"published":"2024-07-20"},{"cvss_score":7.5,"headline":"Bazarr Arbitrary file read in /system/backup/download/ endpoint","id":"CVE-2023-50264","kev_date_added":null,"published":"2023-12-15"},{"cvss_score":5.3,"headline":"Bazarr Blind Server-Side Request Forgery (SSRF) in the /test/\u003cprotocol\u003e/ endpoint","id":"CVE-2023-50266","kev_date_added":null,"published":"2023-12-15"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-07","vendors":["morpheus65535"]},"summary":"An attacker can read arbitrary files from the server via the /api/swaggerui/static endpoint due to lack of filename validation.","url":"https://insights.sbomify.com/CVE-2023-50265/"}