dbcve.org
Wordpress Vertical Image SliderWordPress extension · I13websolution

CVE-2023-24413

MEDIUM · 6.1 CVSS v3.1 Published 2023-08-08
Fix available
A fix is available. Upgrade to 1.2.17 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 WordPress vertical image slider plugin <= 1.2.16 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 I Thirteen Web Solution WordPress vertical image slider plugin versions 1.2.16 and below. Attackers can inject malicious JavaScript code through URL parameters that are reflected in the plugin's output without proper sanitization or output encoding.

MitigationUpdate the plugin to the latest version available from the WordPress repository, or disable and remove the plugin if no update is available.

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
Wordpress Vertical Image SliderWordPress extension
Affected:< 1.2.17

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. Verify the plugin is installed
    Locate the plugin directory in wp-content/plugins/ or check the WordPress admin under Plugins > Installed Plugins for 'Vertical Image Slider' or 'I13websolution Wordpress Vertical Image Slider'
    Affected if The plugin appears in the WordPress plugin directory or plugin list
  2. Determine the installed version
    Open the main plugin PHP file (typically vertical-image-slider.php or similar in the plugin directory) and check the plugin header for the Version field, or examine the readme.txt file
    Affected if Version is 1.2.16 or below, or any version less than 1.2.17
  3. Confirm the plugin is active
    Check WordPress admin under Plugins > Installed Plugins to see if the plugin is activated, or query the wp_options table for the active_plugins option
    Affected if The plugin is currently active on the WordPress site
  4. Identify reflected URL parameter usage
    Examine the plugin's PHP files for direct use of $_GET, $_REQUEST, or similar superglobals that are output to the page without sanitization functions such as esc_html(), esc_attr(), or esc_url()
    Affected if The code outputs URL parameters directly in HTML without proper output encoding

The environment is affected if the I13websolution Vertical Image Slider plugin is installed, active, and running version 1.2.16 or below (less than 1.2.17), with unsanitized URL parameters being reflected in the plugin's 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.2.17 or later
Fixed in 1.2.17
Interim mitigation

Update the plugin to the latest version available from the WordPress repository, or disable and remove the plugin if no update is available.

Recommended fix High confidence

Vertical Image Slider version 1.2.17

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Vertical Image Slider' plugin by I Thirteen Web Solution
  4. Click 'Update now' if an update is available, or manually upload version 1.2.17 of the plugin
  5. Verify the plugin is running version 1.2.17 after updating

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

Fix this in Wordpress Vertical Image Slider Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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