{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-50259 exists.","fix":"No fix has been published for CVE-2023-50259 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-50259 is a medium-severity server-side request forgery vulnerability in pymedusa Medusa, published on 22 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-50259 and fix it if it is affected.\n\nWhat it is: CVE-2023-50259 is a medium-severity server-side request forgery vulnerability in pymedusa Medusa, published on 22 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-50259 exists.\n\nAffected product: pymedusa Medusa. 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-50259/ (Markdown: https://insights.sbomify.com/CVE-2023-50259/index.md)","id":"CVE-2023-50259","markdown":"https://insights.sbomify.com/CVE-2023-50259/index.md","name":"CVE-2023-50259","record":{"aliases":["GHSA-8mcr-vffr-jwxv"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Medusa video manager","requires_auth":"none","summary":"Unauthenticated attackers can trigger blind SSRF via the testslack endpoint, allowing them to craft POST requests on behalf of the Medusa server.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"medusa","vendor":"pymedusa"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Medusa is an automatic video library manager for TV shows. Versions prior to 1.0.19 are vulnerable to unauthenticated blind server-side request forgery (SSRF). The `testslack` request handler in `medusa/server/web/home/handler.py` does not validate the user-controlled `slack_webhook` variable and passes it to the `notifiers.slack_notifier.test_notify` method, then `_notify_slack` and finally `_send_slack` method,  which sends a POST request to the user-controlled URL on line 103 in `/medusa/notifiers/slack.py`, which leads to a blind server-side request forgery (SSRF). This issue allows for crafting POST requests on behalf of the Medusa server. Version 1.0.19 contains a fix for the issue.","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":"Blind SSRF in /home/testslack endpoint","id":"CVE-2023-50259","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2023"},"n_packages":0,"n_references":5,"next":{"headline":"Wazuh's vulnerability in host_deny AR script allows arbitrary command execution","id":"CVE-2023-50260"},"packages":[],"prev":{"headline":"Blind SSRF in `/home/testdiscord` endpoint","id":"CVE-2023-50258"},"products":["Medusa"],"published":"2023-12-22","related":[{"cvss_score":8.3,"headline":"OS Command Injection via GIT_PATH in pymedusa","id":"CVE-2023-28627","kev_date_added":null,"published":"2023-03-27"},{"cvss_score":5.3,"headline":"Blind SSRF in `/home/testdiscord` endpoint","id":"CVE-2023-50258","kev_date_added":null,"published":"2023-12-22"}],"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-11-27","vendors":["pymedusa"]},"summary":"Unauthenticated attackers can trigger blind SSRF via the testslack endpoint, allowing them to craft POST requests on behalf of the Medusa server.","url":"https://insights.sbomify.com/CVE-2023-50259/"}