# CVE-2025-34433: AVideo < 20.1 Unauthenticated RCE via Predictable Installation Salt

> Unauthenticated attackers can achieve remote code execution by brute-forcing a predictable installation salt to inject malicious payloads into the notification API.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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:** 19 Dec 2025
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-hv75-87h9-4p5h

## What is CVE-2025-34433?

CVE-2025-34433 is a critical code injection vulnerability in World Wide Broadcast Network AVideo, published on 19 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AVideo versions 14.3.1 prior to 20.1 contain an unauthenticated remote code execution vulnerability caused by predictable generation of an installation salt using PHP uniqid(). The installation timestamp is exposed via a public endpoint, and a derived hash identifier is accessible through unauthenticated API responses, allowing attackers to brute-force the remaining entropy. The recovered salt can then be used to encrypt a malicious payload supplied to a notification API endpoint that evaluates attacker-controlled input, resulting in arbitrary code execution as the web server user.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2025-34433 being exploited?

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

Public exploit code:

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-34433 and fix it if it is affected.

What it is: CVE-2025-34433 is a critical code injection vulnerability in World Wide Broadcast Network AVideo, published on 19 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-34433 exists.

Affected product: World Wide Broadcast Network 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-34433/ (Markdown: https://insights.sbomify.com/CVE-2025-34433/index.md)
```

## Sources

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

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