dbcve.org
Slider RevolutionWordPress extension · Themepunch

CVE-2024-4092

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-02
Fix available
A fix is available. Upgrade to 6.7.8 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 ‘htmltag’ parameter in all versions up to, and including, 6.7.7 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. 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.7 contain a stored Cross-Site Scripting vulnerability in the 'htmltag' parameter. Authenticated users with administrator privileges (or authors if the capability is extended) can inject arbitrary JavaScript through insufficient input sanitization and improper output escaping, causing the malicious script to execute whenever users access affected pages.

MitigationUpdate Slider Revolution to version 6.7.8 or later to patch this vulnerability. Until updated, limit the ability to configure Slider Revolution to only trusted administrators and consider additional WAF rules for XSS protection.

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

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. Verify Slider Revolution plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Slider Revolution' by Themepunch, or check the plugin directory for /wp-content/plugins/revslider/
    Affected if The plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin Plugins page, click on 'View Details' for Slider Revolution to display the version number, or inspect the main plugin file (e.g., revslider.php) for the Version header comment
    Affected if The displayed version is less than 6.7.8 (e.g., 6.7.7, 6.7.6, etc.)
  3. Identify users with plugin configuration access
    Review WordPress user roles that have access to Slider Revolution settings. Check if any users with Author role have been granted capability to edit sliders (default is Administrator only)
    Affected if Multiple user accounts with Administrator or extended Author capabilities exist and have slider editing privileges
  4. Inspect slider configurations for suspicious htmltag values
    Access Slider Revolution > Slider Grid, open each slider, check Slide Editor > HTML Tags / Layer > Attributes for unexpected script tags, event handlers (onload, onerror, onmouseover), or javascript: URLs in the htmltag parameter
    Affected if Any slider contains script tags, javascript: prefixes, or HTML event handlers in the htmltag field that were not intentionally added by your team

You are affected if Slider Revolution version is below 6.7.8 AND any user with editor-level access has created or modified sliders containing malicious scripts in the htmltag parameter.

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.8 or later
Fixed in 6.7.8
Interim mitigation

Update Slider Revolution to version 6.7.8 or later to patch this vulnerability. Until updated, limit the ability to configure Slider Revolution to only trusted administrators and consider additional WAF rules for XSS protection.

Recommended fix High confidence

Slider Revolution 6.7.8

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find Slider Revolution in the plugin list
  4. Click 'Update now' if an update is available, or manually update to version 6.7.8
  5. Verify the update was successful by checking the plugin version

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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