Polo Video GalleryWordPress extension · Bplugins
CVE-2021-24415
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 Polo Video Gallery – Best wordpress video gallery plugin WordPress plugin through 1.2 does not sanitise or validate the parameters from its shortcode, allowing users with a role as low as contributor to set Cross-Site Scripting payload in them which will be triggered in the page/s with the embed malicious shortcode
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 Polo Video Gallery WordPress plugin (versions through 1.2) fails to sanitize or validate parameters passed to its shortcode, allowing stored XSS injection. Users with contributor-level access can embed malicious JavaScript payloads via the shortcode that execute when other users view the affected pages.
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
Polo Video GalleryWordPress extension
<= 1.2CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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.
-
Verify Polo Video Gallery plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Polo Video Gallery' by Bplugins. Note the installed version number.Affected if Plugin is installed and version is 1.2 or lower
-
Search for shortcode usage in contentUse WordPress search or database query to search post_content, postmeta, and options tables for the shortcode strings '[polo_video_gallery]', '[polo_video]', or similar patterns used by this plugin.Affected if The shortcode is present in any published content (posts, pages, or custom post types)
-
Check for untrusted user rolesNavigate to Users > All Users in WordPress admin. Review which users have 'Contributor' or lower-level roles. These roles can create content with shortcodes.Affected if Any user with Contributor or lower role exists who has published or can publish content containing the shortcode
-
Review plugin source for output escapingAccess the plugin files via FTP or file manager. Examine the main plugin PHP file (typically polo-video-gallery.php or similar) and locate the shortcode handler function. Search for use of esc_attr(), esc_html(), sanitize_text_field(), or wp_kses() on shortcode attributes.Affected if Shortcode attributes are NOT sanitized/escaped before output (no esc_attr, esc_html, sanitize_text_field, or wp_kses found in shortcode handler)
User is affected if the Polo Video Gallery plugin version 1.2 or below is installed AND the shortcode is in use on the site AND untrusted users can create content with that shortcode.
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 dataUpgrade to a patched version of the plugin that implements proper sanitization (e.g., esc_attr(), sanitize_text_field()) on all shortcode parameters, or remove the plugin if no fix is available.
Fix this in Polo Video Gallery
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-24415 — 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-2021-24415 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