# CVE-2026-120409: The All-in-One Video Gallery WordPress plugin before 5.1.1 does not check whether a video is password protected before serving it through it


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-3v4w-8jh3-gmw5

## What is CVE-2026-120409?

CVE-2026-120409 is a medium-severity vulnerability in Unknown All-in-One Video Gallery, published on 9 Nov 2026. 

### Official description

The All-in-One Video Gallery  WordPress plugin before 5.1.1 does not check whether a video is password protected before serving it through its standalone player page and its download link, allowing unauthenticated visitors to obtain the media source of password-protected videos, such as unlisted YouTube or Vimeo links and external file URLs.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-120409 being exploited?

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

Public exploit code:

- All-in-One Video Gallery < 5.1.1 - Unauthenticated Password-Protected Video Source Disclosure (nuclei): http/cves/2026/CVE-2026-120409.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120409 is a medium-severity vulnerability in Unknown All-in-One Video Gallery, published on 9 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120409 exists.

Affected product: Unknown All-in-One Video Gallery. 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-120409/ (Markdown: https://insights.sbomify.com/CVE-2026-120409/index.md)
```

## Sources

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

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