dbcve.org
Fv Flowplayer Video PlayerWordPress extension · Foliovision

CVE-2022-25613

MEDIUM · 5.4 CVSS v3.1 Published 2022-04-04
Fix available
A fix is available. Upgrade to after 7.5.18.727 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Authenticated Persistent Cross-Site Scripting (XSS) vulnerability in FV Flowplayer Video Player (WordPress plugin) versions <= 7.5.18.727 via &fv_wp_flowplayer_field_splash parameter.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Authenticated Persistent Cross-Site Scripting (XSS) vulnerability in FV Flowplayer Video Player WordPress plugin versions <= 7.5.18.727. The fv_wp_flowplayer_field_splash parameter (used for specifying splash/cover images) does not properly sanitize user input before storage, allowing stored malicious scripts to execute when other users view affected pages.

MitigationUpdate FV Flowplayer Video Player plugin to version > 7.5.18.727, or implement proper sanitization of the fv_wp_flowplayer_field_splash parameter using WordPress sanitization functions (sanitize_url/sanitize_text_field) and output escaping (esc_url/esc_attr) at all points where the parameter is stored and displayed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Fv Flowplayer Video PlayerWordPress extension
Affected:<= 7.5.18.727

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify FV Flowplayer plugin is installed
    Navigate to WordPress admin Dashboard > Plugins and check if 'FV Flowplayer Video Player' appears in the installed plugins list
    Affected if Plugin is present in the WordPress installation
  2. Identify installed plugin version
    In the Plugins list, look for the version number displayed under the FV Flowplayer plugin name, or check the plugin header in /wp-content/plugins/fv-wordpress-flowplayer/fv-flowplayer.php
    Affected if Version number is 7.5.18.727 or lower
  3. Check database for splash image entries
    Query the WordPress postmeta table for any entries with meta_key containing 'fv_wp_flowplayer_field_splash' or 'splash' using phpMyAdmin or WP-CLI: wp postmeta list --meta_key=like_flowplayer
    Affected if Any splash image meta entries exist in the database
  4. Inspect stored splash image values for suspicious content
    Review the meta_value of splash image entries for unsanitized content such as javascript: URLs, event handlers (onclick, onerror), or script tags. Use: wp postmeta list --meta_key=like_splash --format=csv
    Affected if Any meta_value contains URL schemes other than http:// or https://, or contains HTML/script content

User is affected if FV Flowplayer plugin version 7.5.18.727 or lower is installed AND the fv_wp_flowplayer_field_splash parameter has been used with unsanitized input containing malicious scripts or non-standard URL schemes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 7.5.18.727
Interim mitigation

Update FV Flowplayer Video Player plugin to version > 7.5.18.727, or implement proper sanitization of the fv_wp_flowplayer_field_splash parameter using WordPress sanitization functions (sanitize_url/sanitize_text_field) and output escaping (esc_url/esc_attr) at all points where the parameter is stored and displayed.

Recommended fix Moderate confidence

Any version higher than 7.5.18.727 (e.g., 7.5.18.728 or latest stable release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate FV Flowplayer Video Player in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. After updating, verify the plugin is running version 7.5.18.728 or later
  6. 6. Clear any site caches if caching plugins are in use
  7. 7. Test video playback functionality to confirm the update did not break existing features
Caveat Minor - review plugin settings after upgrade as some configuration changes may occur

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fv Flowplayer Video Player Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-25613 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-25613 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data