# CVE-2026-33297: AVideo has an IDOR - Any Admin Can Set Another User's Channel Password via setPassword.json.php

> Attackers can bypass channel access controls because a logic error coerces all channel passwords to zero, allowing trivial guessing.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Mar 2026
- **Updated:** 23 Mar 2026
- **Also known as:** GHSA-6547-8hrg-c55m

## What is CVE-2026-33297?

CVE-2026-33297 is a medium-severity vulnerability in Wwbn Avideo, published on 23 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

WWBN AVideo is an open source video platform. Prior to version 26.0, the `setPassword.json.php` endpoint in the CustomizeUser plugin allows administrators to set a channel password for any user. Due to a logic error in how the submitted password value is processed, any password containing non-numeric characters is silently coerced to the integer zero before being stored. This means that regardless of the intended password, the stored channel password becomes 0, which any visitor can trivially guess to bypass channel-level access control. Version 26.0 contains a patch for the issue.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

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 25.0 | None |
| `wwbn/avideo` | Packagist | All versions to 25.0 | None |

Products: Wwbn Avideo.

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

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

## Is CVE-2026-33297 being exploited?

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

## 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-2026-33297 and fix it if it is affected.

What it is: CVE-2026-33297 is a medium-severity vulnerability in Wwbn Avideo, published on 23 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33297 exists.

Affected packages and fixed versions:
- wwbn/avideo (Packagist): affected all versions up to 25.0; no fix listed
- wwbn/avideo (Packagist): affected all versions up to 25.0; 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-2026-33297/ (Markdown: https://insights.sbomify.com/CVE-2026-33297/index.md)
```

## Sources

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

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