dbcve.org
Transition SliderWordPress extension · Creativeinteractivemedia

CVE-2024-37215

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-22
Fix available
A fix is available. Upgrade to after 2.20.3 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in creativeinteractivemedia Transition Slider – Responsive Image Slider and Gallery allows Stored XSS.This issue affects Transition Slider – Responsive Image Slider and Gallery: from n/a through 2.20.3.

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

The Transition Slider WordPress plugin fails to properly sanitize user-supplied input in its slider/gallery functionality, allowing authenticated attackers to inject malicious JavaScript that gets stored in the database and executed when other users view the affected content.

MitigationUpdate to version 2.20.4 or later where the vendor has addressed the input sanitization. Until patched, restrict administrative access and consider deploying a WAF rule to detect XSS payloads.

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
Transition SliderWordPress extension
Affected:<= 2.20.3

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

CVSS:3.1/AV:N/AC:L/PR:L/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 Transition Slider plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Transition Slider' or check the plugins directory for the transition-slider folder
    Affected if Plugin is present in the WordPress installation
  2. Identify installed plugin version
    Check the plugin header in wp-content/plugins/transition-slider/version.php or view the main plugin file for the Version: comment, or look at the plugin details in WordPress admin plugins list
    Affected if Version number is 2.20.3 or lower
  3. Determine if slider/gallery content exists
    Query the WordPress database: SELECT * FROM wp_posts WHERE post_type IN ('ts-slider', 'ts-gallery') AND post_status != 'trash'; (table prefix may vary)
    Affected if Any slider or gallery posts exist in the database
  4. Inspect stored content for potential XSS payloads
    Examine the post_content and meta values from any ts-slider or ts-gallery entries for suspicious patterns like <script tags, javascript: URIs, event handlers (onload, onerror, onclick), or encoded payloads
    Affected if Stored content contains unsanitized user input with script tags, javascript: protocols, or HTML event handlers

The environment is affected if the Transition Slider plugin version is 2.20.3 or lower and any slider/gallery content exists in the database that may contain injected malicious scripts.

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 2.20.3
Interim mitigation

Update to version 2.20.4 or later where the vendor has addressed the input sanitization. Until patched, restrict administrative access and consider deploying a WAF rule to detect XSS payloads.

Recommended fix Moderate confidence

Transition Slider 2.20.4 or latest available version

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Transition Slider – Responsive Image Slider and Gallery'
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, clear any caching plugins or server-side caches
  6. 6. Verify the plugin is running on the latest version by checking the plugins page

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

Fix this in Transition Slider Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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