# CVE-2026-82643: WWBN AVideo Unauthenticated Rate Limit Bypass via preauthorize.json.php

> Attackers can bypass rate limits to perform password guessing and trigger excessive two-factor emails, risking account takeover and service disruption.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Aug 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-5fcm-q2vr-hhjh

## What is CVE-2026-82643?

CVE-2026-82643 is a medium-severity vulnerability in WWBN AVideo, published on 30 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WWBN AVideo contains an unauthenticated credential submission vulnerability in plugin/Live/api/preauthorize.json.php that accepts credentials over GET without rate limiting. Attackers can submit correct credentials repeatedly to trigger uncapped two-factor confirmation emails and perform sustained password guessing attacks against user accounts.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2026-82643?


## How do I fix CVE-2026-82643?

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

## Is CVE-2026-82643 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82643 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82643 and fix it if it is affected.

What it is: CVE-2026-82643 is a medium-severity vulnerability in WWBN AVideo, published on 30 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82643 exists.

Affected product: WWBN AVideo. 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-2026-82643/ (Markdown: https://insights.sbomify.com/CVE-2026-82643/index.md)
```

## Sources

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

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