dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-49773

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/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
Subscriber Cross Site Scripting (XSS) in FV Flowplayer Video Player < 7.5.51.7212 versions.

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 stored Cross Site Scripting (XSS) vulnerability exists in FV Flowplayer Video Player where authenticated subscriber-level users can inject malicious JavaScript code through video player parameters. The flaw allows the script to persist and execute when other users view the affected video content.

MitigationUpdate FV Flowplayer Video Player to version 7.5.51.7212 or later to patch the XSS vulnerability. Until the update is applied, consider restricting subscriber-level user capabilities or deploying WAF rules to filter malicious script payloads.

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

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
Low

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

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 Video Player is installed
    Locate the FV Flowplayer plugin in your WordPress installation under wp-content/plugins or via the WordPress admin plugins page
    Affected if The plugin is present and active in the WordPress environment
  2. Determine the installed plugin version
    Check the plugin header in the main PHP file (typically fv-flowplayer.php) or view the version displayed in the WordPress admin plugins list
    Affected if The installed version is lower than 7.5.51.7212 (the patched release)
  3. Review user role capabilities
    In WordPress admin, go to Users > Roles or check the FV Flowplayer settings to determine if subscriber-level users have the ability to create, edit, or modify video entries and their parameters
    Affected if Subscriber-level users are permitted to add or modify video player configurations
  4. Inspect video player parameters for malicious scripts
    Examine the video entries in the FV Flowplayer database tables (commonly wp_fv_player_videos or similar) or through the admin interface, focusing on player parameter fields where XSS could be injected
    Affected if Any video entries contain suspicious JavaScript tags, event handlers, or script URLs in player parameter fields
  5. Check for recent unauthorized video modifications
    Review the activity log or revision history for the FV Flowplayer videos to identify any unexpected changes made by subscriber-level accounts
    Affected if Subscriber-level accounts have created or modified video entries with unusual parameter values

Your environment is affected if FV Flowplayer Video Player is installed with a version below 7.5.51.7212 and subscriber-level users have permission to add or modify video player parameters, allowing stored XSS payloads to persist and execute for other users viewing the videos.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update FV Flowplayer Video Player to version 7.5.51.7212 or later to patch the XSS vulnerability. Until the update is applied, consider restricting subscriber-level user capabilities or deploying WAF rules to filter malicious script payloads.

Recommended fix High confidence

FV Flowplayer Video Player version 7.5.51.7212 or later

  1. Update the FV Flowplayer Video Player plugin to version 7.5.51.7212 or later through the WordPress plugin administration panel
  2. Verify the update was successfully applied by checking the plugin version number
  3. Clear any caching mechanisms that may serve stale content
  4. Test that the subscriber XSS vulnerability is no longer present by attempting to submit malicious script content as a subscriber user

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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