CVE-2026-121985 in FV Flowplayer Video Player Plugin
Summary
by MITRE • 11/20/2026
The FV Flowplayer Video Player plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 7.5.57.7212 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires the plugin's 'Parse Vimeo and YouTube links' setting to be enabled, which wires do_shortcode into the comment_text filter chain and allows the [fvplayer] shortcode to be rendered from comment content.
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 11/21/2026
The FV Flowplayer Video Player plugin for WordPress contains a critical security vulnerability identified as Stored Cross-Site Scripting within versions up to 7.5.57.7212. This flaw stems directly from insufficient input sanitization and output escaping mechanisms when processing user-supplied data, specifically targeting the comment parameter associated with video player interactions. The nature of this vulnerability allows unauthenticated attackers to inject arbitrary web scripts into pages that are subsequently rendered by other users. When a victim accesses a page containing the injected script, the malicious code executes within their browser context, potentially leading to session hijacking, credential theft, or defacement depending on the attacker's objectives and the privileges associated with the affected user account.
The technical root cause of this vulnerability lies in how the plugin handles shortcodes embedded within comment content. Specifically, when the setting labeled Parse Vimeo and YouTube links is enabled, the plugin wires the do_shortcode function into the WordPress comment_text filter chain. This configuration allows any shortcode present in a comment to be parsed and rendered dynamically. Because the input validation does not adequately restrict or sanitize special characters that could form part of a script tag or event handler, an attacker can craft a malicious payload using valid HTML or JavaScript syntax disguised as part of a video link structure. The lack of proper output escaping ensures that once this content is stored in the database and later retrieved for display, it is executed by the browser rather than being treated as plain text data.
From an operational perspective, the impact of this vulnerability extends beyond simple script execution due to its persistent nature. As a Stored Cross-Site Scripting flaw, the malicious payload remains on the server until manually removed from the database or through administrative intervention. This means that every user who views the affected page is exposed to the attack without requiring any specific interaction with the attacker's initial injection point beyond viewing the compromised content. The requirement for an unauthenticated actor to exploit this vulnerability significantly lowers the barrier to entry, allowing individuals with no prior access credentials to compromise site integrity and user security. This persistence amplifies the blast radius of a single successful exploitation event across all visitors who encounter the tainted comment during their browsing session.
To mitigate these risks, immediate action is required by website administrators managing installations of this plugin. The most effective remediation strategy involves updating the FV Flowplayer Video Player to version 7.5.58 or later, where the developers have addressed the input validation and output escaping deficiencies. For environments where an update cannot be applied immediately due to compatibility constraints, a temporary mitigation involves disabling the Parse Vimeo and YouTube links setting within the plugin configuration. This action prevents the do_shortcode function from processing comment content in this specific manner, thereby neutralizing the attack vector until a permanent patch can be deployed. Additionally, implementing Web Application Firewall rules that detect and block common XSS payloads in comment fields can provide an additional layer of defense against exploitation attempts while administrative controls are being adjusted.
This vulnerability aligns with CWE-79, which classifies Improper Neutralization of Input During Web Page Generation commonly known as Cross-site Scripting. The attack methodology corresponds to the MITRE ATT&CK technique T1059.007, specifically JavaScript execution within a browser environment via stored payloads. Understanding these classifications helps security teams contextualize the severity and potential exploitation paths associated with this flaw. By addressing both the immediate technical deficiency in code handling and implementing broader defensive measures such as input validation policies and output encoding standards, organizations can significantly reduce their exposure to similar injection-based attacks across their WordPress infrastructure.