# CVE-2023-49599: WWBN AVideo Insufficient Entropy vulnerbaility

> Insufficient entropy in salt generation allows attackers to brute force password recovery codes and escalate privileges to admin.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jan 2024
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-wqcc-qf63-c2x4

## What is CVE-2023-49599?

CVE-2023-49599 is a critical vulnerability in Wwbn Avideo, published on 10 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An insufficient entropy vulnerability exists in the salt generation functionality of WWBN AVideo dev master commit 15fed957fb. A specially crafted series of HTTP requests can lead to privilege escalation. An attacker can gather system information via HTTP requests and brute force the salt offline, leading to forging a legitimate password recovery code for the admin user.

Weakness: CWE-331 (Insufficient Entropy)

## Which versions are affected by CVE-2023-49599?

2 open source packages ship an affected version, including wwbn/avideo. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wwbn/avideo` | Packagist | All versions to 12.4 | None |
| `wwbn/avideo` | Packagist | All versions to 12.4 | None |

Products: Wwbn Avideo.

## How do I fix CVE-2023-49599?

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

## Is CVE-2023-49599 being exploited?

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

## Other vulnerabilities in Wwbn Avideo

- [CVE-2026-40911](https://insights.sbomify.com/CVE-2026-40911/): WWBN AVideo YPTSocket WebSocket Broadcast Relay Leads to Unauthenticated Cross-User JavaScript Execution via Client-Side eval() Sinks (critical 10.0)
- [CVE-2026-33478](https://insights.sbomify.com/CVE-2026-33478/): AVideo Multi-Chain Attack: Unauthenticated Remote Code Execution via Clone Key Disclosure, Database Dump, and Command Injection (critical 10.0)
- [CVE-2022-30534](https://insights.sbomify.com/CVE-2022-30534/): Command injection in AVideo (critical 9.9)
- [CVE-2022-30547](https://insights.sbomify.com/CVE-2022-30547/): Path traversal in AVideo (critical 9.9)
- [CVE-2022-32572](https://insights.sbomify.com/CVE-2022-32572/): Command injection in AVideo (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-49599 and fix it if it is affected.

What it is: CVE-2023-49599 is a critical vulnerability in Wwbn Avideo, published on 10 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-49599 in the wild and no public exploit code.

Affected packages and fixed versions:
- wwbn/avideo (Packagist): affected all versions up to 12.4; no fix listed
- wwbn/avideo (Packagist): affected all versions up to 12.4; no fix listed

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-2023-49599/ (Markdown: https://insights.sbomify.com/CVE-2023-49599/index.md)
```

## Sources

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

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