{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-47930 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-47930 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-47930 is a medium-severity missing authorization vulnerability in zulip, published on 15 May 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-47930 and fix it if it is affected.\n\nWhat it is: CVE-2025-47930 is a medium-severity missing authorization vulnerability in zulip, published on 15 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-47930 in the wild and no public exploit code.\n\nAffected product: zulip. 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-2025-47930/ (Markdown: https://insights.sbomify.com/CVE-2025-47930/index.md)","id":"CVE-2025-47930","markdown":"https://insights.sbomify.com/CVE-2025-47930/index.md","name":"CVE-2025-47930","record":{"aliases":["GHSA-rqg7-xfqg-v7q5"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Zulip team chat","requires_auth":"low_privilege","summary":"Attackers can bypass channel creation restrictions by creating private channels and changing their privacy settings to public.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"zulip","vendor":"zulip"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Zulip is an open-source team chat application. Starting in version 10.0 and prior to version 10.3, the \"Who can create public channels\" access control mechanism can be circumvented by creating a private or web-public channel, and then changing the channel privacy to public. A similar technique works for creating private channels without permission, though such a process requires either the API or modifying the HTML, as we do mark the \"private\" radio button as disabled in such cases. Version 10.3 contains a patch.","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":"Zulip Server has access control bypass for restrictions on creation of specific channel types","id":"CVE-2025-47930","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"LibreNMS stored Cross-site Scripting vulnerability in poller group name","id":"CVE-2025-47931"},"packages":[],"prev":{"headline":"DumbDrop vulnerable to DOM XSS via file upload","id":"CVE-2025-47929"},"products":["zulip"],"published":"2025-05-15","related":[{"cvss_score":8.6,"headline":"RabbitMQ exposes ports with weak default secrets in Zulip Server","id":"CVE-2021-43799","kev_date_added":null,"published":"2022-01-25"},{"cvss_score":8,"headline":"Crafted link in Zulip message can cause disclosure of credentials","id":"CVE-2022-35962","kev_date_added":null,"published":"2022-08-29"},{"cvss_score":7.5,"headline":"Auth bypass in zulip","id":"CVE-2016-4427","kev_date_added":null,"published":"2022-07-28"},{"cvss_score":6.8,"headline":"Cross-site Scripting (XSS) - Stored in zulip/zulip","id":"CVE-2021-3866","kev_date_added":null,"published":"2022-01-20"},{"cvss_score":6.5,"headline":"Unauthorized user can register an account in specific configurations in Zulip","id":"CVE-2023-28623","kev_date_added":null,"published":"2023-05-19"},{"cvss_score":6.5,"headline":"Ineffective expiration validation for invitation links in Zulip","id":"CVE-2021-43791","kev_date_added":null,"published":"2021-12-02"},{"cvss_score":6.1,"headline":"Zulip: Path Traversal in Import","id":"CVE-2026-26058","kev_date_added":null,"published":"2026-04-03"}],"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-05-16","vendors":["zulip"]},"summary":"Attackers can bypass channel creation restrictions by creating private channels and changing their privacy settings to public.","url":"https://insights.sbomify.com/CVE-2025-47930/"}