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

CVE-2026-7556

HIGH · 7.2 CVSS v3.1 Published 2026-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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 for WordPress is vulnerable to Stored Cross-Site Scripting via the comment text in all versions up to, and including, 7.5.49.7212 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires an administrator to have enabled the non-default 'Parse Vimeo and YouTube links' (parse_comments) plugin setting, and requires a submitted comment to be approved by an administrator before the payload is publicly delivered.

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

The FV Flowplayer Video Player plugin for WordPress contains a stored XSS vulnerability in its comment parsing functionality. Due to insufficient input sanitization and output escaping on comment text, unauthenticated attackers can inject malicious JavaScript when the parse_comments setting is enabled and a comment is approved.

MitigationUpdate the plugin to the latest version once available and disable the 'Parse Vimeo and YouTube links' setting until a patch is applied. Review existing approved comments for malicious 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
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Confirm FV Flowplayer plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'FV Flowplayer Video Player' in the list
    Affected if The plugin is not installed or has been removed entirely
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find FV Flowplayer Video Player, and note the version number displayed
    Affected if Version is 7.5.49.7212 or lower
  3. Verify if Parse Vimeo and YouTube links setting is enabled
    In WordPress admin, go to Flowplayer > Settings (or the plugin settings page) and locate the 'Parse Vimeo and YouTube links' or 'parse_comments' setting. Check whether it is turned on or off
    Affected if The setting is enabled (checked/on)
  4. Inspect recent comments for video links
    In WordPress admin, go to Comments and review approved comments, particularly those containing YouTube or Vimeo URLs (e.g., youtube.com/watch, youtu.be, vimeo.com)
    Affected if Any approved comments contain raw YouTube or Vimeo links that may have been processed by the plugin

A user is affected if the FV Flowplayer plugin version is 7.5.49.7212 or lower AND the 'Parse Vimeo and YouTube links' setting is enabled, as this creates the conditions for stored XSS execution in approved comments

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 the plugin to the latest version once available and disable the 'Parse Vimeo and YouTube links' setting until a patch is applied. Review existing approved comments for malicious payloads.

Recommended fix Moderate confidence

Latest version newer than 7.5.49.7212 (check WordPress plugin repository for current 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 install the latest version
  5. 5. After updating, verify the plugin version is newer than 7.5.49.7212
  6. 6. If using the 'Parse Vimeo and YouTube links' (parse_comments) setting, review recent approved comments for any suspicious payloads and remove them

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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