Fv Flowplayer Video PlayerWordPress extension · Foliovision
CVE-2023-25066
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in FolioVision FV Flowplayer Video Player plugin <= 7.5.30.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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the FolioVision FV Flowplayer Video Player plugin for WordPress allows attackers to trick authenticated administrators into performing unintended actions such as plugin settings changes or stored XSS attacks by leveraging the lack of anti-CSRF tokens on sensitive forms and AJAX endpoints.
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
<= 7.5.30.7212CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Verify FV Flowplayer plugin is installedLog into WordPress admin dashboard and navigate to Plugins > Installed Plugins, or check the /wp-content/plugins/fv-wordpress-flowplayer directory exists on the serverAffected if The plugin is not present in the WordPress installation
-
Check the installed plugin versionIn WordPress admin, find FV Flowplayer Video Player in the plugins list and note the version number displayed, or inspect the main plugin file (e.g., fv-wordpress-flowplayer.php) for the 'Version' header commentAffected if The version number is 7.5.30.7212 or lower
-
Inspect plugin for anti-CSRF implementationExamine the plugin PHP files for presence of nonces or token validation on AJAX actions (look for functions like wp_verify_nonce, check_ajax_referer, or nonce fields in forms). Check admin form files and AJAX handler files in the plugin directoryAffected if No anti-CSRF nonce validation is found in state-changing forms or AJAX endpoints
The environment is affected if the FV Flowplayer Video Player plugin version is 7.5.30.7212 or lower and sensitive admin forms or AJAX endpoints lack anti-CSRF token validation.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the FV Flowplayer Video Player plugin to the latest version beyond 7.5.30.7212 which implements proper anti-CSRF tokens, SameSite cookies, and origin validation on state-changing requests.
Fix this in Fv Flowplayer Video Player
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25066 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-25066 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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