Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSubmit crafted comment with malicious shortcode align attribute
-
DeliveryComment stored in WordPress database
-
Exploitparse_comments applies do_shortcode on comment_text
-
ExecutionUnescaped align value rendered to page visitors
-
PersistScript executes in victim browsers
-
ImpactSession/credential theft or admin action
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the administrator to have enabled the plugin's 'Parse Vimeo and YouTube links' (parse_comments) setting, which registers do_shortcode on the comment_text filter and causes attacker-supplied shortcode attributes stored in comments to be processed; this is the exact gating condition and it is not the default. It also requires that the site accept comments (the input path for unauthenticated attackers) and that a user subsequently view the page containing the injected comment for the script to fire. Limiting factors: if parse_comments is disabled (default), comment text is not shortcode-processed and the flaw is not reachable; impact is confined to client-side script execution in visitors' browsers (C:L/I:L, no availability impact) on the vulnerable plugin versions <= 7.5.55.7212. |
| Impact | This is a medium-severity stored XSS (CVSS 5.4, CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N) whose real-world priority is tempered by a hard configuration precondition. The signals are mostly consistent rather than conflicting: AV:N/PR:N reflect that an unauthenticated attacker can inject via a comment, S:C reflects that the stored script executes in the context of other users/pages, and AC:H reflects the dependency on a non-default setting. The vuln.today decision label is 'this_month' (not act_now/emergency), and there is no CISA KEV listing and no EPSS score in the provided data, so there is no evidence of active or widespread exploitation. No public exploit is identified in the supplied references - they are a Wordfence advisory, plugin source lines, and the fix commit, none of which is verified working exploit code. Data gaps to note explicitly: EPSS probability is MISSING and KEV status is absent (treat as not-listed), so quantitative exploitation likelihood cannot be derived; the concrete fixed release version number is not stated in the input (only the fixing commit is provided). Net assessment: a genuine but conditional stored-XSS issue that warrants patching on a normal maintenance cadence rather than emergency response, because exploitation requires the administrator to have enabled a non-default comment-parsing feature. |
| Exploit ScenarioDerived | On a WordPress site running FV Flowplayer Video Player (<= 7.5.55.7212) where an administrator has enabled the 'Parse Vimeo and YouTube links' (parse_comments) setting, an unauthenticated attacker submits a comment containing the plugin's shortcode with a malicious 'align' attribute. Because do_shortcode is applied to comment_text and the 'align'/lightbox_align value is rendered without sanitization or output escaping, the injected script is stored and then executes in the browser of every subsequent visitor who views that page. No public exploit is identified at time of analysis, and the high attack complexity (AC:H) stems from the required non-default configuration rather than from a difficult trigger. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 30, 2026
Stored cross-site scripting in the FV Flowplayer Video Player plugin for WordPress (all versions up to and including 7.5.55.7212) lets unauthenticated attackers submit comments whose shortcode 'align' attribute value is neither sanitized on input nor escaped on output, so script executes in the browsers of visitors who later view the affected page. The flaw is only reachable when an administrator has enabled the plugin's 'Parse Vimeo and YouTube links' (parse_comments) setting, which registers do_shortcode on the comment_text filter; that condition is not the default, which is why the CVSS 3.1 score of 5.4 (AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N) carries a high attack-complexity metric despite unauthenticated access. Impact is confined to client-side script execution in visitors' browsers with no availability impact, no public exploit has been identified at time of analysis, and priority is assessed as this month rather than immediate.
RemediationAI
Upstream fix available (commit); released patched version not independently confirmed. The correction is in commit c00ff09bc438266617b22053d82a397e5a8967be of the foliovision/fv-wordpress-flowplayer repository (https://github.com/foliovision/fv-wordpress-flowplayer/commit/c00ff09bc438266617b22053d82a397e5a8967be), which replaces the unchecked lightbox_align attribute with a strict allowlist of 'left', 'right' and 'center'; the available source data does not state a plugin release number that contains this commit, so the installed version should be verified as carrying the fix rather than assumed from a version string. Where an update cannot be applied immediately, the gating precondition is the practical control: disabling the plugin's 'Parse Vimeo and YouTube links' (parse_comments) setting stops comment text from being processed by do_shortcode and makes the vulnerable rendering path unreachable, with the trade-off that Vimeo and YouTube links posted in comments will no longer be auto-embedded. Disabling or restricting comments on affected sites removes the unauthenticated injection path altogether, at the cost of losing visitor discussion on those pages. Reviewing existing comment content for player shortcodes with unexpected align values is worthwhile before re-enabling shortcode parsing in comments. Consult the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/30215025-58d0-48e4-88bd-7ec2b0460c94?source=cve) for the vendor-side detail on fixed versions.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is the foliovision/fv-wordpress-flowplayer WordPress plugin (CPE cpe:2.3:a:foliovision:fv_flowplayer_video_player:*:*:*:*:*:*:*:*, a wildcard covering every published version through 7.5.55.7212). The root cause class is CWE-79 (Improper Neutralization of Input During Web Page Generation), realized here as stored XSS through the plugin's shortcode handling: the 'align' shortcode attribute of the player shortcode is written into lightbox markup without validation or escaping. The referenced source locations trace the data path from shortcode registration and attribute consumption (controller/shortcodes.php line 103, controller/frontend.php line 664) into the lightbox rendering model (models/lightbox.php lines 276, 285 and 414). The upstream fix at commit c00ff09bc438266617b22053d82a397e5a8967be shows the remediation pattern - the free-form attribute check on lightbox_align was replaced with a strict allowlist test against 'left', 'right' and 'center' using in_array(..., true) - confirming that unexpected attribute values were previously accepted and emitted. The attacker-controlled input path is WordPress comment text, which only reaches the shortcode engine when the administrator-enabled parse_comments option causes the plugin to register do_shortcode on the comment_text filter; with that setting off, comment content is not shortcode-processed and the vulnerable rendering path is unreachable.
Know when Fv Flowplayer Video Player gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
Unauthenticated comment injection gives PR:N and AV:N; dependency on the non-default parse_comments setting justifies AC:H; stored XSS crossing into visitors' browser context gives S:C with C:L/I:L and no availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The FV Flowplayer Video Player plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment (shortcode attribute 'align')' parameter in all versions up to, and including, 7.5.55.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. This requires the plugin's 'Parse Vimeo and YouTube links' (parse_comments) setting to be enabled by an administrator, which causes the plugin to register do_shortcode on the comment_text filter, allowing attacker-supplied shortcode attributes stored in comments to be rendered unescaped to all subsequent visitors.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Fv Flowplayer Video Player
View allThe FV Flowplayer Video Player WordPress plugin is vulnerable to Reflected Cross-Site Scripting via the player_id parame
The FV Flowplayer Video Player plugin before 7.3.14.727 for WordPress allows email subscription XSS. Rated medium severi
The FV Flowplayer Video Player plugin before 7.3.15.727 for WordPress allows email subscription SQL injection. Rated cri
A SQL injection vulnerability exists in the FolioVision FV Flowplayer Video Player plugin before 7.3.19.727 for WordPres
The FV Flowplayer Video Player plugin before 7.3.15.727 for WordPress allows guests to obtain the email subscription lis
Authenticated file upload bypass in the FV Flowplayer Video Player plugin for WordPress (all versions up to and includin
The FV Flowplayer Video Player plugin for WordPress is vulnerable to time-based SQL Injection via the ‘exclude’ paramete
Cross-Site Request Forgery (CSRF) vulnerability in FolioVision FV Flowplayer Video Player plugin <= 7.5.30.7212 versions
Contributor-level WordPress users can abuse the FV Flowplayer Video Player plugin's server-side URL fetch routine to pro
Stored cross-site scripting in the FV Flowplayer Video Player WordPress plugin (all versions up to and including 7.5.54.
PHP object injection in FV Flowplayer Video Player 8.3.4 and earlier allows an authenticated WordPress user with the Woo
Authenticated (author or higher user role) SQL Injection (SQLi) vulnerability discovered in FV Flowplayer Video Player W
EUVD-2026-114260
GHSA-7cxc-cmc3-r76j
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB