# CVE-2026-27732: AVideo has Authenticated Server-Side Request Forgery via downloadURL in aVideoEncoder.json.php

> Authenticated attackers can exploit an SSRF vulnerability in AVideo to access internal network resources and retrieve sensitive data.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Feb 2026
- **Updated:** 27 Feb 2026
- **Also known as:** GHSA-h39h-7cvg-q7j6

## What is CVE-2026-27732?

CVE-2026-27732 is a high-severity server-side request forgery vulnerability in Wwbn Avideo, published on 24 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

WWBN AVideo is an open source video platform. Prior to version 22.0, the `aVideoEncoder.json.php` API endpoint accepts a `downloadURL` parameter and fetches the referenced resource server-side without proper validation or an allow-list. This allows authenticated users to trigger server-side requests to arbitrary URLs (including internal network endpoints). An authenticated attacker can leverage SSRF to interact with internal services and retrieve sensitive data (e.g., internal APIs, metadata services), potentially leading to further compromise depending on the deployment environment. This issue has been fixed in AVideo version 22.0.

Weakness: CWE-918 (Server-Side Request Forgery)

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

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

Products: Wwbn Avideo.

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

Upgrade wwbn/avideo to 22.0 or later.

## Is CVE-2026-27732 being exploited?

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

What it is: CVE-2026-27732 is a high-severity server-side request forgery vulnerability in Wwbn Avideo, published on 24 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-27732 in the wild and no public exploit code.

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

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

## Sources

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

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