dbcve.org
Fv Flowplayer Video PlayerWordPress extension · Foliovision

CVE-2019-14801

CRITICAL · 9.8 CVSS v3.0 Published 2019-08-09
Fix available
A fix is available. Upgrade to 7.3.15.727 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
The FV Flowplayer Video Player plugin before 7.3.15.727 for WordPress allows email subscription SQL injection.

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

A SQL injection vulnerability exists in the FV Flowplayer Video Player plugin for WordPress's email subscription feature. Attackers can inject malicious SQL queries through unsanitized email input, potentially allowing database compromise, data exfiltration, or escalation to remote code execution. This critical flaw affects all versions before 7.3.15.727 and is exploitable remotely without authentication.

MitigationUpdate the FV Flowplayer Video Player plugin to version 7.3.15.727 or later to patch the SQL injection vulnerability. If immediate updating is not feasible, disable the email subscription functionality and implement a WAF rule to block SQL injection attempts.

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

CVSS:3.0/AV:N/AC:L/PR:N/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. Confirm FV Flowplayer plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'FV Flowplayer Video Player' in the list, or inspect the file /wp-content/plugins/fv-wordpress-flowplayer/ with directory listing
    Affected if The FV Flowplayer Video Player plugin appears in the installed plugins list
  2. Identify the installed plugin version
    In WordPress admin, click on the FV Flowplayer entry in Plugins > Installed Plugins to view the plugin details and version number, or read the 'Version' field from the plugin's main PHP file header in /wp-content/plugins/fv-wordpress-flowplayer/
    Affected if The displayed version number is less than 7.3.15.727 (e.g., 7.3.15, 7.3.14, 6.x, etc.)
  3. Verify the email subscription feature is active
    Check if the plugin's email subscription functionality is enabled by reviewing the plugin settings at Flowplayer > Global Settings > Email, or look for the subscription-related shortcode or widget being used on the site
    Affected if The email subscription feature is enabled or the subscription form is present on any page/post of the site
  4. Confirm remote access to the subscription endpoint
    Test that the subscription endpoint is accessible externally by submitting a POST request to the WordPress admin-ajax.php or the plugin's subscription handler URL with an 'email' parameter, without requiring authentication
    Affected if The endpoint responds and accepts email input without requiring a logged-in WordPress session

The environment is affected if FV Flowplayer Video Player plugin version is below 7.3.15.727 AND the email subscription feature is active and accessible remotely.

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 7.3.15.727 or later
Fixed in 7.3.15.727
Interim mitigation

Update the FV Flowplayer Video Player plugin to version 7.3.15.727 or later to patch the SQL injection vulnerability. If immediate updating is not feasible, disable the email subscription functionality and implement a WAF rule to block SQL injection attempts.

Recommended fix High confidence

7.3.15.727 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate FV Flowplayer Video Player in the plugin list
  4. Click 'Update Now' if an update is available, or check the plugin page for the latest version
  5. Verify the installed version is 7.3.15.727 or higher under Plugins > Installed Plugins
  6. Test the email subscription functionality to confirm the fix is working

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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