dbcve.org
Continuous Image Carousel With LightboxWordPress extension · I13websolution

CVE-2023-28776

MEDIUM · 6.1 CVSS v3.1 Published 2023-06-22
Fix available
A fix is available. Upgrade to after 1.0.15 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 · high confidence

An unauthenticated reflected Cross-Site Scripting (XSS) vulnerability exists in the Continuous Image Carousel With Lightbox WordPress plugin versions 1.0.15 and earlier. Attackers can inject malicious JavaScript through unsanitized user input that gets reflected back in the HTTP response, potentially enabling session hijacking or actions performed on behalf of authenticated users.

MitigationUpdate the plugin to version 1.0.16 or later, which contains the security patch. If an update is unavailable, consider disabling the plugin until a patched version is released.

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 Carousel With LightboxWordPress extension
Affected:<= 1.0.15

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 plugins folder (wp-content/plugins/) for a directory named 'continuous-image-carousel-with-lightbox' or similar naming pattern from I13websolution
    Affected if The plugin directory exists on the server
  2. Determine installed plugin version
    Open the plugin's main PHP file or readme.txt in the plugin directory and locate the Version header or entry in the file header comment
    Affected if The reported version is 1.0.15 or earlier
  3. Verify plugin is active
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or query the wp_options table for option_name = 'active_plugins'
    Affected if The plugin appears in the list of active plugins
  4. Identify the vulnerable parameter exposure
    Since this is a reflected XSS, examine HTTP requests to plugin endpoints for unsanitized parameters. Common WordPress plugin XSS vectors include GET/POST parameters reflected in output without escaping. Test by submitting common input like <script>alert(1)</script> to plugin URLs and observing if it reflects unescaped in the response
    Affected if User-supplied input reflects in the HTTP response without HTML encoding

If the Continuous Image Carousel With Lightbox plugin is installed with version 1.0.15 or earlier and is actively loaded on the site, the reflected XSS vulnerability is present and exploitable for unauthenticated attackers.

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 a release after 1.0.15
Interim mitigation

Update the plugin to version 1.0.16 or later, which contains the security patch. If an update is unavailable, consider disabling the plugin until a patched version is released.

Recommended fix Moderate confidence

Latest version available in WordPress Plugin Directory (version > 1.0.15)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate 'Continuous Image Carousel With Lightbox' by I Thirteen Web Solution
  4. 4. Check the current version installed (should be <= 1.0.15)
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. If no update appears in WordPress, visit the WordPress Plugin Directory and manually download the latest version
  7. 7. Deactivate and delete the current plugin, then upload and install the latest version from the plugin repository
  8. 8. Verify the update was successful and test that the plugin functionality works as expected

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

Fix this in Continuous Image Carousel With Lightbox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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