{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-50931 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-50931 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-50931 is a high-severity vulnerability in n/a, published on 9 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-50931 and fix it if it is affected.\n\nWhat it is: CVE-2023-50931 is a high-severity vulnerability in n/a, published on 9 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-50931 in the wild and no public exploit code.\n\nAffected product: n/a. 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-50931/ (Markdown: https://insights.sbomify.com/CVE-2023-50931/index.md)","id":"CVE-2023-50931","markdown":"https://insights.sbomify.com/CVE-2023-50931/index.md","name":"CVE-2023-50931","record":{"aliases":["GHSA-2q4q-6wrc-q22h"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Bitbucket plugin","requires_auth":"none","summary":"An attacker can trick a logged-in Bitbucket administrator into modifying S/Notify plugin settings via CSRF, potentially disabling email encryption.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"s-notify","vendor":"savignano"}],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AC:L/AV:N/A:L/C:H/I:H/PR:N/S:U/UI:R","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"An issue was discovered in savignano S/Notify before 2.0.1 for Bitbucket. While an administrative user is logged on, the configuration settings of S/Notify can be modified via a CSRF attack. The injection could be initiated by the administrator clicking a malicious link in an email or by visiting a malicious website. If executed while an administrator is logged on to Bitbucket, an attacker could exploit this to modify the configuration of the S/Notify app on that host. This can, in particular, lead to email notifications being no longer encrypted when they should be.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Cross-site request forgery in n/a","id":"CVE-2023-50931","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2023-50932"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2023-50930"},"products":["n/a"],"published":"2024-01-09","related":[{"cvss_score":8.3,"headline":"Cross-site request forgery in n/a","id":"CVE-2023-50930","kev_date_added":null,"published":"2024-01-09"},{"cvss_score":8.3,"headline":"Cross-site request forgery in n/a","id":"CVE-2023-50932","kev_date_added":null,"published":"2024-01-09"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2024-23735","kev_date_added":null,"published":"2024-04-10"},{"cvss_score":5.4,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-23737","kev_date_added":null,"published":"2024-07-01"},{"cvss_score":5.2,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-23734","kev_date_added":null,"published":"2024-04-10"}],"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-04-17","vendors":["n/a"]},"summary":"An attacker can trick a logged-in Bitbucket administrator into modifying S/Notify plugin settings via CSRF, potentially disabling email encryption.","url":"https://insights.sbomify.com/CVE-2023-50931/"}