{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-41961 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-41961 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-41961 is a medium-severity vulnerability in bigbluebutton, published on 16 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-41961 and fix it if it is affected.\n\nWhat it is: CVE-2022-41961 is a medium-severity vulnerability in bigbluebutton, published on 16 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-41961 in the wild and no public exploit code.\n\nAffected product: bigbluebutton. 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-2022-41961/ (Markdown: https://insights.sbomify.com/CVE-2022-41961/index.md)","id":"CVE-2022-41961","markdown":"https://insights.sbomify.com/CVE-2022-41961/index.md","name":"CVE-2022-41961","record":{"aliases":["GHSA-wxjp-h88g-7fqg"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Web conferencing system","requires_auth":"low_privilege","summary":"Attackers can bypass user bans in BigBlueButton by joining meetings with alternative accounts linked to the same external ID.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"bigbluebutton","vendor":"bigbluebutton"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-346","name":"Origin Validation Error"},{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"BigBlueButton is an open source web conferencing system. Versions prior to 2.4-rc-6 are subject to Ineffective user bans. The attacker could register multiple users, and join the meeting with one of them. When that user is banned, they could still join the meeting with the remaining registered users from the same extId. This issue has been fixed by improving permissions such that banning a user removes all users related to their extId, including registered users that have not joined the meeting. This issue is patched in versions 2.4-rc-6 and 2.5-alpha-1. There are no workarounds.","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":"BigBlueButton subject to Ineffective user bans","id":"CVE-2022-41961","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"BigBlueButton contains Incorrect Authorization for setting emoji status","id":"CVE-2022-41962"},"packages":[],"prev":{"headline":"BigBlueButton contains DoS via failed authToken validation","id":"CVE-2022-41960"},"products":["bigbluebutton"],"published":"2022-12-16","related":[{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2020-27602","kev_date_added":null,"published":"2020-10-21"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2020-27605","kev_date_added":null,"published":"2020-10-21"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2020-12443","kev_date_added":null,"published":"2020-04-29"},{"cvss_score":8.4,"headline":"Hardcoded credentials in n/a","id":"CVE-2020-27613","kev_date_added":null,"published":"2020-10-21"},{"cvss_score":8.1,"headline":"Cross-site Scripting (XSS) - Generic in bigbluebutton/bigbluebutton","id":"CVE-2021-4143","kev_date_added":null,"published":"2022-01-19"},{"cvss_score":7.5,"headline":"BigBlueButton vulnerable to DoS via PollSubmitVote GraphQL mutation","id":"CVE-2025-61601","kev_date_added":null,"published":"2025-10-09"},{"cvss_score":7.5,"headline":"BigBlueButton vulnerable to Chat DoS via invalid reactionEmojiId","id":"CVE-2025-61602","kev_date_added":null,"published":"2025-10-09"}],"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":["bigbluebutton"]},"summary":"Attackers can bypass user bans in BigBlueButton by joining meetings with alternative accounts linked to the same external ID.","url":"https://insights.sbomify.com/CVE-2022-41961/"}