# CVE-2023-47861: Cross-site scripting in AVideo

> An attacker can execute arbitrary JavaScript in a victim's browser by tricking them into visiting a malicious webpage in WWBN AVideo.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Jan 2024
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-339f-fg4x-gwcm

## What is CVE-2023-47861?

CVE-2023-47861 is a critical cross-site scripting vulnerability in Wwbn Avideo, published on 10 Jan 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A cross-site scripting (xss) vulnerability exists in the channelBody.php user name functionality of WWBN AVideo 11.6 and dev master commit 15fed957fb. A specially crafted HTTP request can lead to arbitrary Javascript execution. An attacker can get a user to visit a webpage to trigger this vulnerability.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Wwbn Avideo.

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

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

## Is CVE-2023-47861 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-47861 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-2023-47861 and fix it if it is affected.

What it is: CVE-2023-47861 is a critical cross-site scripting vulnerability in Wwbn Avideo, published on 10 Jan 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-47861 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-2023-47861/ (Markdown: https://insights.sbomify.com/CVE-2023-47861/index.md)
```

## Sources

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

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