Skip to main content
Vulnerability Database/CVE-2026-42695

CVE-2026-42695: FV Flowplayer Video Player XSS Vulnerability

CVE-2026-42695 is a stored XSS vulnerability in FV Flowplayer Video Player that allows attackers to inject malicious scripts into web pages. This article covers the technical details, affected versions up to 7.5.54.7212, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-42695 Overview

CVE-2026-42695 is a stored cross-site scripting (XSS) vulnerability in the FolioVision FV Flowplayer Video Player plugin for WordPress. The flaw affects all versions of fv-wordpress-flowplayer from an unspecified initial release through 7.5.54.7212. Authenticated attackers can inject malicious scripts that persist in the plugin's stored content and execute in the browsers of users who view the affected pages. The vulnerability is tracked under CWE-79 for improper neutralization of input during web page generation. Successful exploitation requires low-privilege authentication and user interaction, and the resulting script execution crosses security scopes within the WordPress site.

Critical Impact

Authenticated attackers can store malicious JavaScript in the plugin that executes in victim browsers, enabling session theft, administrative action hijacking, and defacement of WordPress sites running vulnerable fv-wordpress-flowplayer installations.

Affected Products

  • FolioVision FV Flowplayer Video Player (fv-wordpress-flowplayer) WordPress plugin
  • All versions from n/a through 7.5.54.7212
  • WordPress sites with the plugin installed and activated

Discovery Timeline

  • 2026-10-09 - CVE-2026-42695 published to the National Vulnerability Database (NVD)
  • 2026-10-11 - Last updated in NVD database

Technical Details for CVE-2026-42695

Vulnerability Analysis

The vulnerability resides in how the FV Flowplayer Video Player plugin processes attacker-controlled input during web page generation. The plugin fails to properly neutralize script-bearing input before rendering it in HTML output. Because the payload is stored server-side, it executes every time an affected page is loaded by a visitor or administrator.

The attack scope is marked as changed, meaning the injected script executes in a security context different from the one the attacker originally authenticated to. This increases the blast radius beyond the plugin itself to the entire WordPress site. Confidentiality, integrity, and availability impacts are each limited but non-trivial.

Root Cause

The root cause is missing or insufficient output encoding and input sanitization within the plugin's video configuration or shortcode handling logic. User-supplied values submitted through the plugin interface are written to persistent storage and later echoed into HTML attributes or element bodies without context-appropriate escaping. This allows HTML and JavaScript syntax to break out of the intended data context.

Attack Vector

An authenticated attacker with low-privilege WordPress access, such as a contributor or editor role, submits crafted input through plugin fields that accept video metadata, shortcodes, or player configuration. The payload is stored in the WordPress database. When another user, typically an administrator or site visitor, loads a page that renders the stored content, the injected script executes under the site's origin.

Typical exploitation outcomes include theft of session cookies, forced administrative actions through CSRF-like forged requests, redirection to attacker-controlled infrastructure, and injection of secondary payloads. See the Patchstack advisory for technical specifics.

Detection Methods for CVE-2026-42695

Indicators of Compromise

  • Unexpected <script> tags, javascript: URIs, or event handler attributes stored in wp_posts, wp_postmeta, or plugin-specific tables related to fv-wordpress-flowplayer.
  • Outbound requests from administrator browsers to unfamiliar domains shortly after loading pages containing FV Flowplayer shortcodes.
  • New administrator accounts, modified user roles, or plugin changes made from sessions that align with suspected XSS execution.

Detection Strategies

  • Audit plugin-stored content for HTML tags and encoded script patterns in video titles, descriptions, and shortcode attributes.
  • Enable WordPress audit logging to capture content modifications made by low-privilege users to fields handled by the plugin.
  • Deploy a web application firewall (WAF) rule set that identifies common XSS payload signatures submitted to WordPress admin endpoints.

Monitoring Recommendations

  • Monitor browser Content Security Policy (CSP) violation reports for inline script execution on pages that embed the FV Flowplayer player.
  • Track administrative session anomalies such as unexpected privilege changes, plugin installations, or theme modifications.
  • Alert on egress HTTP requests from editorial users to newly observed external domains following plugin content edits.

How to Mitigate CVE-2026-42695

Immediate Actions Required

  • Update the FV Flowplayer Video Player plugin to a version released after 7.5.54.7212 that addresses CVE-2026-42695.
  • Review user accounts with contributor-level privileges or higher and remove any that are unnecessary or inactive.
  • Scan existing posts, pages, and plugin settings for stored script payloads and remove any malicious content found.

Patch Information

Refer to the Patchstack advisory for CVE-2026-42695 for the latest fixed version and vendor remediation guidance. Apply the patched release through the WordPress plugin updater or by replacing the plugin files directly on the server.

Workarounds

  • Deactivate and remove the FV Flowplayer Video Player plugin until a patched version is applied if an immediate update is not feasible.
  • Restrict low-privilege roles from editing content that uses FV Flowplayer shortcodes via a role management plugin.
  • Enforce a strict Content Security Policy that disallows inline scripts and restricts script sources to trusted origins.
bash
# Example CSP response header for WordPress to limit XSS impact
Header set Content-Security-Policy "default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'self'"

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.