dbcve.org
Slider RevolutionWordPress extension · Themepunch

CVE-2024-4637

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-04
Fix available
A fix is available. Upgrade to 6.7.11 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
The Slider Revolution plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 6.7.10 due to insufficient input sanitization and output escaping on the user supplied Elementor 'wrapperid' and 'zindex' display attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 Slider Revolution WordPress plugin versions up to 6.7.10 suffer from a stored XSS vulnerability in Elementor display attributes. The 'wrapperid' and 'zindex' parameters accept user input without proper sanitization, allowing authenticated contributors or higher to inject malicious JavaScript that executes whenever other users access the affected pages.

MitigationUpdate Slider Revolution plugin to version 6.7.11 or later, which includes proper input sanitization and output escaping for the affected display attributes. Audit existing pages using the plugin for any injected scripts.

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
Slider RevolutionWordPress extension
Affected:< 6.7.11

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 Slider Revolution plugin is installed
    Navigate to WordPress admin > Plugins and locate 'Slider Revolution' in the installed plugins list. Note the version number displayed next to the plugin name.
    Affected if Plugin is installed and version is below 6.7.11
  2. Check plugin version file directly
    Access the plugin main file via FTP or file manager at wp-content/plugins/revslider/revslider.php and read the Version header comment at the top of the file.
    Affected if Version returned is less than 6.7.11
  3. Verify Elementor integration is active
    Check if Elementor page builder is installed and active on the WordPress site. The vulnerability affects Elementor display attributes specifically.
    Affected if Elementor is installed and the site uses Elementor to edit pages/posts where Revolution sliders are embedded
  4. Search database for suspicious wrapperid values
    Query the WordPress database (wp_postmeta table) for meta_key containing 'wrapperid' and examine meta_value for any injected JavaScript patterns such as <script, javascript:, onload, onerror, or event handlers.
    Affected if Any meta_value entries for wrapperid contain unsanitized HTML or JavaScript code
  5. Search database for suspicious zindex values
    Query the WordPress database (wp_postmeta table) for meta_key containing 'zindex' and examine meta_value for any non-numeric content or injected script tags.
    Affected if Any zindex meta_value contains script tags or JavaScript code instead of numeric values

The environment is affected if Slider Revolution plugin version is below 6.7.11 AND Elementor is used to embed sliders AND the database contains unsanitized values in wrapperid or zindex parameters.

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 6.7.11 or later
Fixed in 6.7.11
Interim mitigation

Update Slider Revolution plugin to version 6.7.11 or later, which includes proper input sanitization and output escaping for the affected display attributes. Audit existing pages using the plugin for any injected scripts.

Recommended fix High confidence

Slider Revolution 6.7.11

  1. Update the Slider Revolution plugin to version 6.7.11 or later to address the stored Cross-Site Scripting vulnerability in the Elementor 'wrapperid' and 'zindex' display attributes.

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

Fix this in Slider Revolution 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-2024-4637 — 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-4637 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