# CVE-2026-6439: Cross-site scripting in VideoZen

> Administrators can inject scripts into VideoZen settings, executing code for other users viewing the page.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Apr 2026
- **Updated:** 20 Apr 2026
- **Also known as:** GHSA-gc8m-6q8j-fh75

## What is CVE-2026-6439?

CVE-2026-6439 is a medium-severity cross-site scripting vulnerability in jconti VideoZen, published on 17 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The VideoZen plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to and including 1.0.1. This is due to insufficient input sanitization and output escaping in the videozen_conf() function. The 'lang' POST parameter is stored directly via update_option() without any sanitization, and later echoed inside a <textarea> element without applying esc_textarea() or any equivalent escaping function. This makes it possible for authenticated attackers with Administrator-level access and above to inject arbitrary web scripts into the plugin settings page that will execute whenever any user accesses that page.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-6439 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6439 is a medium-severity cross-site scripting vulnerability in jconti VideoZen, published on 17 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6439 in the wild and no public exploit code.

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

## Sources

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

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