# CVE-2024-34899: AVideo cross-site scripting vulnerability in the view/about.php page

> Attackers can inject malicious scripts into the AVideo web application, potentially stealing user sessions or executing code in victim browsers.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **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:** Yes
- **Published:** 13 May 2024
- **Updated:** 27 Mar 2025
- **Also known as:** GHSA-f98p-2hc5-fm7v

## What is CVE-2024-34899?

CVE-2024-34899 is a medium-severity cross-site scripting vulnerability in Wwbn Avideo, published on 13 May 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

WWBN AVideo 12.4 is vulnerable to Cross Site Scripting (XSS).

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

## Which versions are affected by CVE-2024-34899?

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 | 14.3 |
| `wwbn/avideo` | Packagist | All versions | 14.3 |

Products: Wwbn Avideo.

## How do I fix CVE-2024-34899?

Upgrade wwbn/avideo to 14.3 or later.

## Is CVE-2024-34899 being exploited?

There is no known exploitation of CVE-2024-34899 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-2024-34899 and fix it if it is affected.

What it is: CVE-2024-34899 is a medium-severity cross-site scripting vulnerability in Wwbn Avideo, published on 13 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-34899 in the wild and no public exploit code.

Affected packages and fixed versions:
- wwbn/avideo (Packagist): affected all versions; fixed in 14.3
- wwbn/avideo (Packagist): affected all versions; fixed in 14.3

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

## Sources

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

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