# CVE-2025-34441: AVideo < 20.1 User Information Disclosure via Public API

> Unauthenticated attackers can access sensitive user data like emails and admin status via a public API endpoint in AVideo.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Dec 2025
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-9rpf-6v9q-87h5

## What is CVE-2025-34441?

CVE-2025-34441 is a medium-severity vulnerability in Wwbn Avideo, published on 17 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AVideo versions prior to 20.1 expose sensitive user information through an unauthenticated public API endpoint. Responses include emails, usernames, administrative status, and last login times, enabling user enumeration and privacy violations.

Weakness: CWE-359 (Exposure of Private Personal Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-34441?

It affects 1 product.


Products: Wwbn Avideo.

## How do I fix CVE-2025-34441?

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

## Is CVE-2025-34441 being exploited?

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

Public exploit code:

- AVideo notify.ffmpeg.json.php Unauthenticated RCE via Salt Discovery (metasploit)

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

What it is: CVE-2025-34441 is a medium-severity vulnerability in Wwbn Avideo, published on 17 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-34441 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-2025-34441/ (Markdown: https://insights.sbomify.com/CVE-2025-34441/index.md)
```

## Sources

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

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