dbcve.org
Slider RevolutionWordPress extension · Themepunch

CVE-2024-4581

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 via the plugin's Add Layer widget in all versions up to, and including, 6.7.11 due to insufficient input sanitization and output escaping on the user supplied 'class', 'id', and 'title' attributes. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. NOTE: Successful exploitation of this vulnerability requires an Administrator to give Slider Creation privileges to Author-level users.

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 fails to properly sanitize and escape user-supplied 'class', 'id', and 'title' attributes in its Add Layer widget. This allows authenticated attackers with author-level access (who have been granted Slider Creation privileges by an Administrator) to inject malicious JavaScript that persists and executes when other users access affected pages.

MitigationUpdate Slider Revolution to version 6.7.12 or later. Review and restrict Slider Creation privileges granted to lower-privileged users, and consider implementing Content Security Policy headers as defense-in-depth.

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. Locate the Slider Revolution plugin installation
    Check your WordPress installation's /wp-content/plugins/ folder for the 'revslider' or 'slider-revolution' directory, or query via wp-cli: wp plugin list --search='revslider'
    Affected if The plugin directory exists on the server
  2. Determine the installed plugin version
    Access WordPress admin > Plugins > Slider Revolution and read the version number from the plugin details, or run: wp plugin get revslider --field=version
    Affected if The reported version is lower than 6.7.11 (for example, 6.7.10, 6.6.0, 6.5.0, etc.)
  3. Check if author-level users have Slider Creation privileges
    Navigate to WordPress admin > Users > Roles > Edit Author (or access via Users > User Role Editor if installed), or inspect the wp_options table for 'revslider_user_role' setting; look for 'author' in the allowed roles list
    Affected if Authors (or any user below administrator) have been granted Slider Creation/Editor permissions in the plugin role settings
  4. Verify the Add Layer widget is accessible
    Confirm that a user with author-level access can create or edit a slider in the plugin dashboard by logging in as a test author user and attempting to access Slider Revolution > New Slider or edit an existing slider
    Affected if Authors can access the slider creation interface and Add Layer functionality

You are affected if the installed Slider Revolution version is below 6.7.11 AND author-level users have been granted Slider Creation privileges, allowing them to inject malicious scripts via the Add Layer widget's class, id, or title attributes.

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 to version 6.7.12 or later. Review and restrict Slider Creation privileges granted to lower-privileged users, and consider implementing Content Security Policy headers as defense-in-depth.

Recommended fix High confidence

Slider Revolution 6.7.11 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate Slider Revolution plugin
  4. Click 'Update Now' if an update is available, or manually upload version 6.7.11 or later
  5. Verify the updated version number after update completes
  6. Test the Add Layer widget functionality to ensure the fix works correctly

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

Fix this in Slider Revolution Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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