dbcve.org
Fv Flowplayer Video PlayerWordPress extension · Foliovision

CVE-2022-25607

HIGH · 7.2 CVSS v3.1 Published 2022-03-18
Fix available
A fix is available. Upgrade to after 7.5.15.727 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 (author or higher user role) SQL Injection (SQLi) vulnerability discovered in FV Flowplayer Video Player WordPress plugin (versions <= 7.5.15.727).

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 SQL injection vulnerability in FV Flowplayer Video Player WordPress plugin (versions <= 7.5.15.727) allows users with author or higher roles to inject malicious SQL queries through unsanitized input parameters, potentially enabling data exfiltration or database manipulation.

MitigationUpgrade to FV Flowplayer Video Player version 7.5.15.728 or later which contains the patched code; verify all user inputs in the plugin are properly sanitized before using them in SQL queries.

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.15.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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Check plugin installation directory
    Locate the FV Flowplayer plugin directory in your WordPress installation, typically at wp-content/plugins/fv-flowplayer/ or wp-content/plugins/fv-wordpress-flowplayer/. Verify this directory exists.
    Affected if The plugin directory does not exist (plugin not installed).
  2. Determine installed plugin version
    Open the main plugin file (usually flowplayer.php or fv-flowplayer.php) in the plugin directory and locate the Version header in the plugin comment block. Alternatively, run: wp plugin get fv-flowplayer --field=version
    Affected if The version returned is 7.5.15.727 or lower.
  3. Verify plugin is active
    Run: wp plugin list --status=active --field=name | grep -i flowplayer. Or check via WordPress admin dashboard under Plugins > Active Plugins.
    Affected if The plugin is active and version is <= 7.5.15.727.
  4. Confirm user role configuration
    Check if any user accounts exist with author, editor, or administrator roles who can access the WordPress admin area. Run: wp user list --role=author --field=user_login
    Affected if Any user with author or higher role exists in the system.

You are affected if the FV Flowplayer Video Player plugin is installed, active, and running version 7.5.15.727 or lower, with at least one user holding author-level or higher access.

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.15.727
Interim mitigation

Upgrade to FV Flowplayer Video Player version 7.5.15.728 or later which contains the patched code; verify all user inputs in the plugin are properly sanitized before using them in SQL queries.

Recommended fix High confidence

7.5.16 or latest version available on wordpress.org

  1. Check the currently installed FV Flowplayer Video Player version in WordPress admin under Plugins
  2. Create a full backup of your WordPress site before making any changes
  3. If possible, test the upgrade in a staging environment first
  4. Navigate to Plugins > All Plugins in WordPress admin
  5. Update FV Flowplayer Video Player to the latest version available (7.5.16 or later)
  6. Verify the update was successful by checking the plugin version
  7. Confirm the site functionality remains intact after the upgrade
Caveat Minimal risk - security patch with no major functional changes expected

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-25607 — 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-25607 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