dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-57678

HIGH · 7.1 CVSS v3.1 Published 2026-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges 7 weeks old

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 ('Cross-site Scripting') vulnerability in ThemePunch Slider Revolution allows Reflected XSS. This issue affects Slider Revolution: from 7.0.0 through 7.0.16.

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

Reflected XSS vulnerability in ThemePunch Slider Revolution plugin allows attackers to inject malicious JavaScript via unsanitized input that gets rendered during web page generation. The vulnerability exists in versions 7.0.0 through 7.0.16 and is triggered when user-supplied data is reflected in the application's response without proper output encoding.

MitigationUpdate Slider Revolution to version 7.0.17 or later to obtain the vendor patch. Review and validate all user inputs throughout the application and implement proper output encoding to prevent XSS.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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. Identify Slider Revolution plugin version
    Locate the plugin version in the WordPress admin panel under Plugins > Slider Revolution, or inspect the plugin's main PHP file (typically revslider.php) which contains a version constant or header comment
    Affected if The installed version is 7.0.0 through 7.0.16 (versions prior to 7.0.17)
  2. Confirm the plugin is active
    Verify the Slider Revolution plugin is installed and active on the WordPress site. Check wp-admin > Plugins for the plugin status
    Affected if The plugin is active and the version falls within the affected range
  3. Audit for reflected user input in pages
    Review pages where the plugin is used (such as pages with sliders) and test whether URL parameters or form inputs are reflected in the page output without encoding. Common vectors include search parameters, ID parameters, or custom shortcode attributes
    Affected if User-supplied input is reflected in the HTML output without proper sanitization or encoding on pages utilizing the plugin

If the installed Slider Revolution plugin version is between 7.0.0 and 7.0.16 and user-supplied data can be reflected in the page output, the environment is vulnerable to the reflected XSS in CVE-2026-57678

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Slider Revolution to version 7.0.17 or later to obtain the vendor patch. Review and validate all user inputs throughout the application and implement proper output encoding to prevent XSS.

Recommended fix Moderate confidence

Slider Revolution 7.0.17 or later

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate 'Slider Revolution' in the plugin list
  4. 4. Click 'Update now' if an update is available, or manually upload the newer version
  5. 5. After updating, verify the plugin version shows 7.0.17 or later
  6. 6. Test the affected functionality where the XSS vulnerability was reported to ensure the fix is effective
  7. 7. Clear any site caches (WP Rocket, Autoptimize, etc.) after the update

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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