CVE-2026-49773: FV Flowplayer XSS Vulnerability – Patch Guide & Detection
A cross-site scripting (XSS) vulnerability exists in FV Flowplayer Video Player versions below 7.5.51.7212. An authenticated user can inject malicious scripts that execute in the context of other subscribers' browsers, potentially allowing them to steal session data, redirect users, or perform actions on their behalf. The vulnerability requires user interaction (such as clicking a link) to trigger the attack.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 6.5 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
- Weaknesses (CWE)
- CWE-79
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-06-15 / 2026-06-17
NVD description (verbatim)
Subscriber Cross Site Scripting (XSS) in FV Flowplayer Video Player < 7.5.51.7212 versions.
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-49773 is a stored or reflected XSS flaw (CWE-79) in FV Flowplayer Video Player that allows subscribers to bypass input validation and inject arbitrary JavaScript. The attack vector is network-based with low complexity; exploitation requires valid subscriber credentials and user interaction. The vulnerability has a CVSS 3.1 base score of 6.5 (Medium severity) with a vector of CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L, indicating cross-site scope with limited impact on confidentiality, integrity, and availability.
Business impact
Organizations deploying FV Flowplayer face session hijacking risks, account compromise, and reputational harm if subscriber accounts are weaponized to attack other users. Malicious scripts could harvest credentials, redirect users to phishing sites, or deface video content. Compliance implications exist for platforms handling sensitive subscriber data; XSS can undermine access controls and audit trails. Remediation delays increase exposure window and incident response costs.
Affected systems
FV Flowplayer Video Player versions prior to 7.5.51.7212 are affected. Verify your installed version via the plugin settings or admin panel. The vendor's official documentation and release notes should confirm whether your deployment falls within the vulnerable range.
Exploitability
This vulnerability has moderate exploitability. An attacker must first possess or obtain subscriber credentials, reducing the attack surface compared to unauthenticated XSS. However, once authenticated, the attacker can craft malicious links or comments that, when clicked by other users, execute arbitrary code in their browsers. The requirement for user interaction is a limiting factor, but social engineering tactics make this practical. No known public exploit or active in-the-wild activity has been reported as of the publication date, and the vulnerability is not on the CISA Known Exploited Vulnerabilities (KEV) catalog.
Remediation
Update FV Flowplayer Video Player to version 7.5.51.7212 or later as soon as possible. The vendor has released a patched version that addresses the input validation flaw. After updating, test the video player in your staging environment to confirm functionality before deploying to production. Review and strengthen content security policy (CSP) headers to mitigate residual XSS risk across your platform.
Patch guidance
Upgrade FV Flowplayer Video Player to 7.5.51.7212 or above. Consult the vendor's official advisory and release notes to confirm the patch version and any prerequisite dependencies or compatibility notes. Test patched versions thoroughly in a non-production environment before rolling out to subscriber-facing instances. If you cannot patch immediately, consider disabling user-generated content features or restricting subscriber posting permissions until the update is deployed.
Detection guidance
Monitor application logs for unusual script injection patterns in video player input fields, comments, or metadata. Search for HTML entity-encoded or obfuscated JavaScript keywords (<script>, onerror, onload) in user submissions. Web application firewalls (WAF) should be configured to block or alert on suspicious payloads targeting the video player. Browser-side, check for unexpected network requests or DOM modifications triggered by video player interactions. Review your Content Security Policy violations in browser console logs for signs of XSS attempts.
Why prioritize this
Although this is a Medium-severity vulnerability, prioritize patching because it affects user-facing functionality where subscriber trust is critical. Authenticated XSS in a widely-deployed plugin like a video player can scale quickly if weaponized; a single compromised account can target many users. Organizations with high subscriber counts or sensitive user communities should treat this as a higher-priority patch candidate.
Risk score, explained
The CVSS 6.5 (Medium) score reflects the balance between accessibility factors and impact limitations. Network-based vector and low attack complexity favor the attacker, but the requirement for valid subscriber credentials and user interaction reduces the threat. The cross-site scope means impact is not limited to the vulnerable component, elevating risk beyond a simple information disclosure. However, the limited severity of individual impact factors (L/L/L for C/I/A) prevents a higher rating.
Frequently asked questions
Do we need subscriber credentials to exploit this vulnerability?
Yes. The vulnerability requires valid subscriber authentication, which limits exploitation to attackers who have compromised or obtained legitimate subscriber accounts. This is a meaningful barrier that reduces the overall risk compared to unauthenticated XSS, but compromised credentials are common in breach scenarios.
What versions of FV Flowplayer are safe to use?
Version 7.5.51.7212 and all subsequent releases contain the fix. Verify your current version in the plugin settings or admin dashboard. If you are running anything below 7.5.51.7212, an update is necessary.
Can this vulnerability be exploited without user interaction?
No. The attack requires the target user to click a malicious link or interact with crafted content (e.g., a booby-trapped comment). This user-interaction requirement is a limiting factor but does not eliminate risk, as social engineering can often overcome this barrier.
Is there a workaround if we cannot patch immediately?
Temporary mitigations include disabling user-generated content features, restricting subscriber posting/comment permissions, and implementing strict Content Security Policy (CSP) headers to limit script execution. However, these are band-aids; patching is the definitive fix.
This analysis is provided for informational and educational purposes only. The information reflects the vulnerability description and CVSS scoring at the time of publication. Readers must independently verify patch versions, compatibility, and applicability to their specific deployments. Always test patches in a non-production environment before production deployment. For official guidance, refer to the vendor's security advisories and release notes. SEC.co does not guarantee exploit-free status; vulnerability intelligence evolves as new information emerges. Source: NVD (public-domain), retrieved 2026-07-24. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2016-20070MEDIUMPrivilege Escalation & Stored XSS in WordPress Booking Calendar Contact Form 1.0.23
- CVE-2018-25384MEDIUMStored XSS in Wikidforum 2.20 Allows Authenticated Attackers to Inject Malicious Scripts
- CVE-2019-25731MEDIUMStored XSS in Zuz Music 2.1 Contact Form
- CVE-2019-25737MEDIUMStored XSS in Live Chat Unlimited 2.8.3 – Admin Session Compromise
- CVE-2019-25739MEDIUMGigToDo 1.3 Stored XSS Vulnerability in Proposal Descriptions
- CVE-2019-25742MEDIUMStored XSS in Zoner Real Estate WordPress Theme 4.1.1 – Admin Account Compromise Risk
- CVE-2019-25743MEDIUMWordPress Soliloquy Lite 2.5.6 Stored XSS Vulnerability
- CVE-2019-25744MEDIUMWordPress Popup Builder 3.49 Stored XSS Vulnerability – Exploit Prevention & Patch Guide