dbcve.org
Thumbnail Carousel SliderWordPress extension · I13websolution

CVE-2023-2120

MEDIUM · 6.1 CVSS v3.1 Published 2023-04-18
Fix available
A fix is available. Upgrade to after 1.1.9 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 Thumbnail carousel slider plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the search_term parameter in versions up to, and including, 1.1.9 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.

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 Thumbnail carousel slider WordPress plugin fails to properly sanitize the search_term parameter before outputting it, allowing unauthenticated attackers to inject arbitrary JavaScript through reflected XSS. The vulnerability affects versions up to 1.1.9 and requires user interaction (clicking a crafted link) to execute malicious scripts.

MitigationUpgrade to version 1.2.0 or later which includes proper input sanitization and output escaping for the search_term parameter.

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
Thumbnail Carousel SliderWordPress extension
Affected:<= 1.1.9

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. Confirm plugin installation
    Check the WordPress plugins directory or wp-admin for 'I13websolution Thumbnail Carousel Slider' in the list of installed plugins. Note the installed version number.
    Affected if The plugin is installed and version is 1.1.9 or lower.
  2. Locate plugin version file
    Navigate to wp-content/plugins/thumbnail-carousel-slider/ folder and locate the main PHP file (often includes 'version' in comments or a readme.txt file). Open to find the version definition.
    Affected if The version returned is 1.1.9 or lower, indicating the vulnerable version.
  3. Identify vulnerable parameter exposure
    Access the page where the carousel search functionality is exposed (typically a frontend page with the carousel shortcode). Inspect the HTML source for the search_term parameter in the URL or form submission.
    Affected if The search_term parameter is present and reflected in the page output without proper escaping.
  4. Test for XSS vulnerability
    Submit a test payload such as 'test"><script>alert(1)</script>' via the search_term parameter in the URL (e.g., ?search_term=test"><script>alert(1)</script>). Observe if the script tags appear unescaped in the page response.
    Affected if The payload is rendered as raw HTML/JavaScript instead of being escaped, confirming the XSS vulnerability exists.

If the plugin is installed at version 1.1.9 or below and the search_term parameter reflects unescaped input in the page output, the environment is affected by this CVE.

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.1.9
Interim mitigation

Upgrade to version 1.2.0 or later which includes proper input sanitization and output escaping for the search_term parameter.

Recommended fix Moderate confidence

1.2.0 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Thumbnail Carousel Slider' plugin
  4. Check if the current version is 1.1.9 or lower
  5. If vulnerable, click 'Update Now' to upgrade to the latest version
  6. Alternatively, navigate to Plugins > Add New > Upload and upload a newer version of the plugin from the WordPress plugin repository

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

Fix this in Thumbnail Carousel Slider Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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