dbcve.org
Video Carousel Slider With LightboxWordPress extension · I13websolution

CVE-2023-2710

MEDIUM · 6.1 CVSS v3.1 Published 2023-05-16
Fix available
A fix is available. Upgrade to 1.0.23 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 video carousel slider with lightbox plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the search_term parameter in versions up to, and including, 1.0.22 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. CVE-2023-32797 may be a duplicate of this.

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 video carousel slider with lightbox WordPress plugin versions up to 1.0.22 contains a reflected Cross-Site Scripting vulnerability. The search_term parameter is not properly sanitized before output, allowing attackers to inject arbitrary JavaScript via malicious URLs that trick users into clicking them.

MitigationUpdate the plugin to a patched version once available. Until then, warn users against clicking untrusted links to this plugin's functionality.

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
Video Carousel Slider With LightboxWordPress extension
Affected:< 1.0.23

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate the plugin installation
    Access your WordPress site via FTP or file manager, navigate to /wp-content/plugins/ and look for a folder named 'video-carousel-slider-with-lightbox' or similar I13websolution plugin
    Affected if The plugin folder exists on the server
  2. Identify the installed version
    Open the main plugin PHP file (usually video-carousel-slider-with-lightbox.php) and look for a 'Version:' comment in the file header, or check the plugin details in WordPress admin under Plugins > Installed Plugins
    Affected if The version number displayed is less than 1.0.23 (for example, 1.0.22, 1.0.21, etc.)
  3. Test the vulnerable parameter
    Send a crafted request to any page where the plugin is active, adding ?search_term=<script>alert(1)</script> to the URL and check if the script executes or is reflected unsanitized in the page response
    Affected if The search_term value is reflected in the HTML output without encoding or sanitization (you see the literal script tag in the page source)
  4. Check plugin configuration
    In WordPress admin, go to the plugin settings page (usually under Settings or a dedicated menu item for this plugin) and verify if the search/lightbox feature is enabled and publicly accessible
    Affected if The plugin search functionality is enabled and accessible to unauthenticated users

You are affected if the I13websolution Video Carousel Slider With Lightbox plugin is installed at a version below 1.0.23 AND the search_term parameter is reflected unsanitized in page output.

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.0.23 or later
Fixed in 1.0.23
Interim mitigation

Update the plugin to a patched version once available. Until then, warn users against clicking untrusted links to this plugin's functionality.

Recommended fix High confidence

1.0.23

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Video Carousel Slider With Lightbox' plugin
  4. Click 'Update now' if an update is available, or manually update to version 1.0.23
  5. Verify the plugin is running version 1.0.23 or higher after updating

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

Fix this in Video Carousel Slider With Lightbox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-2710 — 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-2023-2710 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