# CVE-2026-92579: AVideo through 29.0 Broken Access Control via CSRF Exemption Basename Collision

> Attackers can force authenticated users to log out via CSRF due to broken access control in AVideo's plugin system.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-3hg6-6x7m-5xr8, GHSA-4687-wm68-8h9w

## What is CVE-2026-92579?

CVE-2026-92579 is a medium-severity vulnerability in WWBN AVideo, published on 16 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

In AVideo through 29.0, the autoCSRFGuard() function maintains a hardcoded allowlist of exempt basenames tested without directory context, allowing plugin files matching core filenames to inherit CSRF exemptions. The LoginWordPress plugin file login.json.php inherits an exemption and unconditionally logs out authenticated users on cross-site POST requests before validating credentials.

Weakness: CWE-289 (Authentication Bypass by Alternate Name)

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


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

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

## Is CVE-2026-92579 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92579 is a medium-severity vulnerability in WWBN AVideo, published on 16 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92579 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-2026-92579/ (Markdown: https://insights.sbomify.com/CVE-2026-92579/index.md)
```

## Sources

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

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