# CVE-2021-45900: Auth bypass in n/a

> Attackers can bypass authentication to impersonate users and perform state-changing actions in Vivoh Webinar Manager.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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:** 30 Mar 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-q25m-8fmg-wgf6

## What is CVE-2021-45900?

CVE-2021-45900 is a medium-severity authentication bypass vulnerability in n/a, published on 30 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vivoh Webinar Manager before 3.6.3.0 has improper API authentication. When a user logs in to the administration configuration web portlet, a VIVOH_AUTH cookie is assigned so that they can be uniquely identified. Certain APIs can be successfully executed without proper authentication. This can let an attacker impersonate as victim and make state changing requests on their behalf.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2021-45900?

It affects 1 product.


Products: Vivoh Webinar Manager.

## How do I fix CVE-2021-45900?

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

## Is CVE-2021-45900 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-45900 and fix it if it is affected.

What it is: CVE-2021-45900 is a medium-severity authentication bypass vulnerability in n/a, published on 30 Mar 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-2021-45900 in the wild and no public exploit code.

Affected product: n/a. 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-2021-45900/ (Markdown: https://insights.sbomify.com/CVE-2021-45900/index.md)
```

## Sources

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

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