# CVE-2026-56342: AVideo - Server-Side Request Forgery in Live/test.php via statsURL Parameter

> Authenticated administrators can exploit an SSRF vulnerability in AVideo to access internal services and cloud metadata endpoints, potentially exposing sensitive credentials and configuration data.

- **Severity:** Medium 6.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jun 2026
- **Updated:** 22 Jun 2026
- **Also known as:** GHSA-qmrg-93c4-g93f

## What is CVE-2026-56342?

CVE-2026-56342 is a medium-severity server-side request forgery vulnerability in AVideo, published on 20 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

AVideo through version 27.0 contains a server-side request forgery vulnerability in plugin/Live/test.php that allows authenticated administrators to read arbitrary URLs via the statsURL parameter, which lacks isSSRFSafeURL() validation and accepts requests to private IP ranges and cloud metadata endpoints. Attackers can exploit this by crafting requests to internal services, cloud metadata endpoints like 169.254.169.254, and localhost to retrieve sensitive information including IAM credentials, internal service responses, and network configuration details.

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

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


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

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

## Is CVE-2026-56342 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-56342 and fix it if it is affected.

What it is: CVE-2026-56342 is a medium-severity server-side request forgery vulnerability in AVideo, published on 20 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56342 exists.

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

## Sources

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

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