CVE-2026-6439
Stored XSS in VideoZen WordPress Plugin Allows Admin Script Injection
Publication date: 2026-04-17
Last updated on: 2026-04-17
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| videozen | plugin | to 1.0.1 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The VideoZen plugin for WordPress has a Stored Cross-Site Scripting (XSS) vulnerability in versions up to and including 1.0.1. This occurs because the plugin does not properly sanitize or escape input in the videozen_conf() function. Specifically, the 'lang' POST parameter is stored directly without sanitization and later displayed inside a textarea element without escaping. This allows authenticated users with Administrator-level access or higher to inject malicious scripts into the plugin settings page, which will execute whenever any user views that page.
How can this vulnerability impact me? :
This vulnerability can allow attackers with Administrator-level access to inject malicious scripts into the plugin settings page. These scripts will execute in the context of any user who accesses that page, potentially leading to unauthorized actions such as stealing session cookies, defacing the site, or performing actions on behalf of other users. Although the attacker needs high-level access to exploit this, the impact includes loss of data integrity and confidentiality.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should update the VideoZen plugin to a version later than 1.0.1 where the issue is fixed.
If an update is not immediately available, restrict Administrator-level access to trusted users only, as the vulnerability requires authenticated Administrator-level access.
Additionally, avoid using the vulnerable 'lang' POST parameter or sanitize and escape inputs properly in the plugin code, specifically applying esc_textarea() or equivalent escaping functions to prevent stored cross-site scripting.