# CVE-2022-41961: BigBlueButton subject to Ineffective user bans

> Attackers can bypass user bans in BigBlueButton by joining meetings with alternative accounts linked to the same external ID.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Dec 2022
- **Updated:** 17 Apr 2025
- **Also known as:** GHSA-wxjp-h88g-7fqg

## What is CVE-2022-41961?

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.

### Official 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.

Weakness: CWE-346 (Origin Validation Error), CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2022-41961?

It affects 1 product.


Products: Bigbluebutton Bigbluebutton.

## How do I fix CVE-2022-41961?

No fix has been published for CVE-2022-41961 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-41961 being exploited?

There is no known exploitation of CVE-2022-41961 in the wild and no public exploit code.

## Other vulnerabilities in bigbluebutton

- [CVE-2020-27602](https://insights.sbomify.com/CVE-2020-27602/): Other in n/a (critical 9.8)
- [CVE-2020-27605](https://insights.sbomify.com/CVE-2020-27605/): Code injection in n/a (critical 9.8)
- [CVE-2020-12443](https://insights.sbomify.com/CVE-2020-12443/): Path traversal in n/a (critical 9.8)
- [CVE-2020-27613](https://insights.sbomify.com/CVE-2020-27613/): Hardcoded credentials in n/a (high 8.4)
- [CVE-2021-4143](https://insights.sbomify.com/CVE-2021-4143/): Cross-site Scripting (XSS) - Generic in bigbluebutton/bigbluebutton (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41961 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2022-41961 in the wild and no public exploit code.

Affected product: bigbluebutton. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-41961/ (Markdown: https://insights.sbomify.com/CVE-2022-41961/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-41961
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-41961
- OSV: https://osv.dev/vulnerability/CVE-2022-41961

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-41961/
Summaries are generated and may contain mistakes; the official description above is the record.