CVE-2026-126005: FV Flowplayer Video Player <= 7.5.57.7212 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'fv_wp_flowplayer_field_src' Parameter
The FV Flowplayer Video Player plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'data[videos][0][fvwpflowplayerfieldsrc]' 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 authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The fvplayerdbsave AJAX endpoint's INSERT path is gated only by a per-user preview nonce and never calls currentusercan(), allowing any authenticated subscriber-level user who possesses their own nonce to store the malicious payload. Exploitation by attackers with subscriber-level access and above requires that administrator has enabled the plugin option fvwpflowplayer['profilevideosenablebio']=true (off by default), which enqueues the shortcode editor and the per-user previewnonce on wp-admin/profile.php for every logged-in user. On a default installation, where that is not configured, the vulnerability requires attackers with contributor-level access and above.
Affected Software
Event History
Frequently Asked Questions
Are default installations exposed to subscriber-level attackers?
No. Subscriber-level exploitation requires the administrator to enable fvwpflowplayer['profile_videos_enable_bio']=true, which is off by default. Without that setting, an attacker needs contributor-level access or higher.
What does an attacker need to exploit this issue?
The attacker must be authenticated to WordPress and have at least subscriber access when the profile-videos option is enabled, or contributor access on the default configuration. They also need their own per-user preview nonce; the affected AJAX save path does not perform a current_user_can() capability check.
What is the impact after a successful exploit?
An attacker can store arbitrary script content through the affected video source parameter. The script executes when another user accesses the page containing the injected payload, potentially exposing or modifying data available in that user's browser session.
What configuration should be checked during triage?
Check whether the FV Flowplayer option fvwpflowplayer['profile_videos_enable_bio'] is enabled. If it is enabled, all logged-in users receive the shortcode editor and per-user preview nonce on wp-admin/profile.php, making subscriber-level exploitation possible.