# CVE-2026-85161: AVideo removePoster.php Cross-Site Request Forgery File Deletion

> Attackers can trick authenticated users into deleting their live poster and thumbnail files via crafted GET requests in AVideo.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Sep 2026
- **Updated:** 3 Sep 2026
- **Also known as:** GHSA-4h63-5723-hq25, GHSA-rqjp-jjmp-m6hm

## What is CVE-2026-85161?

CVE-2026-85161 is a medium-severity vulnerability in WWBN AVideo, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

AVideo through commit c91b5975d contains a cross-site request forgery vulnerability in removePoster.php that lacks forbidIfNotPost or forbidIfInvalidToken checks. Attackers can craft malicious image tags to delete authenticated victims' live poster and thumbnail files via GET requests.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-85161 being exploited?

There is no known exploitation of CVE-2026-85161 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85161 is a medium-severity vulnerability in WWBN AVideo, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-85161 in the wild and no public exploit code.

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

## Sources

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

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