dbcve.org
Continuous Image Carosel With LightboxWordPress extension · I13websolution

CVE-2023-28792

MEDIUM · 6.1 CVSS v3.1 Published 2023-04-07
Fix available
A fix is available. Upgrade to 1.0.16 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
Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in I Thirteen Web Solution Continuous Image Carousel With Lightbox plugin <= 1.0.15 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 · moderate confidence

Unauthenticated reflected cross-site scripting (XSS) vulnerability in the I Thirteen Web Solution Continuous Image Carousel With Lightbox WordPress plugin affecting versions 1.0.15 and below. The vulnerability allows attackers to inject malicious scripts via unsanitized input that gets reflected back in HTTP responses.

MitigationUpdate the plugin to the latest version (if available) which should include proper input sanitization and output encoding to prevent XSS attacks.

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
Continuous Image Carosel With LightboxWordPress extension
Affected:< 1.0.16

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 directory
    Check your WordPress wp-content/plugins directory for a folder named 'continuous-image-carousel-with-lightbox' or similar variant of 'i13-websolution-continuous-image-carousel-with-lightbox'
    Affected if The plugin directory exists on the server
  2. Identify the installed plugin version
    If the plugin directory exists, check the main plugin PHP file (usually named similar to the directory) for the 'Version' header in the plugin comment block, or use WP-CLI command: wp plugin list --plugin='*carousel*' --format=table
    Affected if The reported version is 1.0.15 or lower, or the Version header cannot be found (which may indicate an older unlisted version)
  3. Confirm the plugin is active
    Check WordPress admin under Plugins > Installed Plugins, or use WP-CLI: wp plugin list --status=active --format=table to see if the plugin appears in the active list
    Affected if The plugin is actively enabled on the WordPress site

You are affected if the I Thirteen Web Solution Continuous Image Carousel With Lightbox plugin is installed, active, and running version 1.0.15 or below, allowing unauthenticated attackers to inject malicious scripts via HTTP parameters that get reflected in the response.

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.16 or later
Fixed in 1.0.16
Interim mitigation

Update the plugin to the latest version (if available) which should include proper input sanitization and output encoding to prevent XSS attacks.

Recommended fix High confidence

1.0.16

  1. Update the Continuous Image Carousel With Lightbox plugin to version 1.0.16 or later through the WordPress admin dashboard under Plugins > Installed Plugins
  2. Alternatively, update via FTP or hosting control panel file manager by replacing the plugin files with version 1.0.16
  3. Verify the update was successful by checking the plugin version in the WordPress admin
  4. Clear any caching plugins or server-side caches after updating
  5. Test the previously vulnerable functionality (any URL parameters that could be reflected) to confirm the XSS vulnerability is remediated

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

Fix this in Continuous Image Carosel With 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-2023-28792 — 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-28792 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