dbcve.org
Slider RevolutionWordPress extension · Themepunch

CVE-2024-8107

MEDIUM · 5.4 CVSS v3.1 Published 2024-10-01
Fix available
A fix is available. Upgrade to after 6.7.18 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 SVG File uploads in all versions up to, and including, 6.7.18 due to insufficient input sanitization and output escaping. 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 the SVG file. By default, this can only be exploited by administrators, but the ability to use and configure Slider Revolution can be extended to authors.

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.18) allows authenticated users with Author-level permissions or higher to upload SVG files. Due to insufficient input sanitization and output escaping, malicious SVG files can contain embedded JavaScript that executes when other users access the uploaded file, resulting in stored XSS.

MitigationUpdate Slider Revolution to version 6.7.19 or later. Until patched, restrict or disable SVG file upload functionality and review user role permissions for Slider Revolution configuration access.

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.18

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. Check if Slider Revolution plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Slider Revolution' or check the wp-content/plugins/revslider directory exists on the server
    Affected if Slider Revolution plugin is present on the WordPress site
  2. Determine the installed version of Slider Revolution
    In WordPress admin, go to Plugins > Installed Plugins > Slider Revolution and view the version number displayed, or check the revslider.php file header for 'Version:' value
    Affected if Version is 6.7.18 or lower (any version up to and including 6.7.18)
  3. Verify if SVG upload is available to Authors
    Log in as a user with Author role and attempt to access the Slider Revolution upload functionality (usually via the plugin's slider creation or media upload features), or check the user role capabilities in WordPress under Users > Roles
    Affected if Users with Author-level permissions can access and use the SVG file upload feature in Slider Revolution
  4. Look for suspicious SVG uploads
    Check the wp-content/uploads directory (and subdirectories) for SVG files, or query the WordPress posts table for attachments with MIME type 'image/svg+xml', especially uploaded by lower-privileged users
    Affected if SVG files exist in the uploads directory, particularly from users with Author-level access or below

A WordPress site is affected if it has Slider Revolution version 6.7.18 or earlier installed AND allows Author-level users to upload SVG files through the plugin.

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

Update Slider Revolution to version 6.7.19 or later. Until patched, restrict or disable SVG file upload functionality and review user role permissions for Slider Revolution configuration access.

Recommended fix Moderate confidence

A version newer than 6.7.18 (check WordPress plugin repository for latest stable release)

  1. 1. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  2. 2. Locate the Slider Revolution plugin in the list
  3. 3. If an update is available, click 'Update Now' to install the latest version
  4. 4. Verify the update was successful by checking the plugin version number
  5. 5. Test SVG file upload functionality to confirm the vulnerability is remediated
  6. 6. Consider implementing additional file upload restrictions at the server level (e.g., disabling SVG uploads entirely or restricting to trusted users only)
Caveat Review plugin settings after upgrade as minor interface changes may occur

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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