dbcve.org
Wp Video LightboxWordPress extension · Tipsandtricks Hq

CVE-2021-24665

MEDIUM · 5.4 CVSS v3.1 Published 2021-08-30
Fix available
A fix is available. Upgrade to 1.9.3 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
The WP Video Lightbox WordPress plugin before 1.9.3 does not escape the attributes of its shortcodes, allowing users with a role as low as contributor to perform Cross-Site Scripting attacks

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 confidence

The WP Video Lightbox WordPress plugin before version 1.9.3 fails to properly escape/sanitize shortcode attributes, allowing stored Cross-Site Scripting (XSS) attacks. Users with contributor-level privileges (lowest role that can create content) can inject malicious JavaScript through shortcode attributes that get rendered without proper output encoding.

MitigationUpdate WP Video Lightbox to version 1.9.3 or later, which implements proper attribute escaping. If immediate update is not possible, disable the plugin until patched.

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
Wp Video LightboxWordPress extension
Affected:< 1.9.3

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify WP Video Lightbox plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Video Lightbox' by Tipsandtricks HQ. Alternatively, check the plugin directory at wp-content/plugins/wp-video-lightbox/ for existence of the plugin files.
    Affected if The plugin is installed and active in WordPress.
  2. Identify installed plugin version
    In WordPress admin_plugins list, find WP Video Lightbox and read the version number displayed below the plugin name. Alternatively, open wp-content/plugins/wp-video-lightbox/wp-video-lightbox.php and look for the 'Version' header in the plugin comment block.
    Affected if The version number is below 1.9.3 (for example, 1.9.2, 1.9.1, 1.9.0, etc.).
  3. Confirm shortcode usage on the site
    Search WordPress posts, pages, and custom post types for the [video_lightbox] shortcode. This can be done via database query: SELECT * FROM wp_posts WHERE post_content LIKE '%[video_lightbox%' (adjust wp_ prefix if different).
    Affected if The shortcode [video_lightbox] is present in any published content.
  4. Inspect shortcode attribute values for potential XSS payloads
    Examine the shortcode attributes in post content for unescaped characters such as quotes, script tags, or javascript: URIs. Example: [video_lightbox video_id="1" anchor_text="<img src=x onerror=alert(1)>"]. Check if attribute values contain HTML or JavaScript that would render as executable code.
    Affected if Shortcode attributes contain raw HTML, JavaScript event handlers, or suspicious patterns that would execute in a browser context.

You are affected if the WP Video Lightbox plugin is installed with a version lower than 1.9.3 and the [video_lightbox] shortcode with potentially malicious attribute values exists on your site.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 1.9.3 or later
Fixed in 1.9.3
Interim mitigation

Update WP Video Lightbox to version 1.9.3 or later, which implements proper attribute escaping. If immediate update is not possible, disable the plugin until patched.

Recommended fix High confidence

WP Video Lightbox version 1.9.3

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find WP Video Lightbox in the plugin list
  4. If the current version is below 1.9.3, click 'Update Now' to upgrade to version 1.9.3
  5. Verify the update completed successfully by checking the plugin version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wp Video Lightbox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-24665 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-24665 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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