CVE-2026-12135
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 · uneditedThe FV Flowplayer Video Player plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'video_player' shortcode 'align' attribute in all versions up to, and including, 7.5.51.7212 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 confidenceThe FV Flowplayer Video Player WordPress plugin fails to sanitize the 'align' attribute in the 'video_player' shortcode and does not properly escape output, allowing stored XSS injection. Authenticated users with contributor-level access can embed malicious JavaScript that executes when other users view affected pages.
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
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm FV Flowplayer plugin is installedNavigate to WordPress admin > Plugins, or inspect the /wp-content/plugins/fv-flowplayer-video-player/ directory for the main plugin file and read its version headerAffected if The plugin is present in the installation
-
Identify installed FV Flowplayer versionRead the version number from the plugin's main PHP file header (usually fv-flowplayer.php) or check via Plugins page in WordPress adminAffected if Version is 7.5.51.7212 or lower (any version prior to the fix)
-
Check for video_player shortcode usageSearch the WordPress database (wp_posts table) for content containing [video_player] shortcode, or use a plugin scanner to list shortcode occurrencesAffected if The shortcode is present in any post, page, or custom post type content
-
Verify shortcode 'align' attribute is in useSearch post content for [video_player] entries that include align= attribute, e.g., grep or SQL query: SELECT * FROM wp_posts WHERE post_content LIKE '%[video_player%align=%'Affected if Any instance of the shortcode with an align attribute is found in published content
-
Review contributor-level user accessCheck WordPress user roles at Users > All Users to confirm contributor or author-level accounts exist, as these roles can use the video_player shortcodeAffected if Any authenticated user with contributor-level or higher access exists on the site
If the FV Flowplayer plugin version is 7.5.51.7212 or lower AND the video_player shortcode with an align attribute is in use on the site, the installation is vulnerable to stored XSS.
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 a version beyond 7.5.51.7212, which should include proper input sanitization for the 'align' attribute and output escaping. If an update is unavailable, apply sanitization (e.g., sanitize_html_class) and escaping (e.g., esc_attr) to the attribute value in the shortcode handler.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12135 — 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-2026-12135 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