# CVE-2026-114633: WWBN AVideo before 29.4.0 Incorrect Authorization via confirmDeleteUser.json.php


- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-m76f-g7j3-5gvv, GHSA-mp89-8x4j-2grx

## What is CVE-2026-114633?

CVE-2026-114633 is a high-severity vulnerability in WWBN AVideo, published on 22 Oct 2026. 

### Official description

WWBN AVideo before 29.4.0 contains an incorrect authorization vulnerability that allows delegated Users Admin accounts to delete or modify administrator accounts. Attackers can submit requests to confirmDeleteUser.json.php or userAddNew.json.php targeting administrators to delete their videos and accounts, or change and demote them.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-114633 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114633 is a high-severity vulnerability in WWBN AVideo, published on 22 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114633 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-114633/ (Markdown: https://insights.sbomify.com/CVE-2026-114633/index.md)
```

## Sources

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

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