dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-6728

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 Sensitive Information Exposure in versions up to, and including, 7.0.9 via the 'get_stream_data()' function. This makes it possible for unauthenticated attackers to extract sensitive data including published password-protected post, page, and product content.

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 7.0.9 contain a sensitive information exposure vulnerability in the get_stream_data() function. This allows unauthenticated attackers to retrieve password-protected content from posts, pages, and products, exposing data that should require authentication to access.

MitigationUpdate Slider Revolution plugin to a version newer than 7.0.9. If immediate update is not possible, restrict access to the vulnerable endpoint via web server configuration or disable the plugin until patching is feasible.

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 look for 'Slider Revolution' in the list, or check the wp-content/plugins/revslider directory exists on the server
    Affected if The plugin is present in the WordPress installation
  2. Determine installed plugin version
    Check the plugin's main PHP file (revslider.php) for the 'Version' header comment in the file header, or view the plugin details in the WordPress plugins page
    Affected if The version is not the latest patched release (this is a zero-day/future CVE so compare against current stable version)
  3. Test for unauthenticated access to get_stream_data
    Send a crafted HTTP request to the WordPress site with a query like ?action=get_stream_data or /wp-json/revslider/v1/stream_data without providing authentication cookies or credentials
    Affected if The endpoint responds with content from password-protected posts, pages, or products without requiring login
  4. Verify password-protected content exposure
    Create a password-protected page or post, then make an unauthenticated request to the vulnerable endpoint and check if the protected content (including the password prompt) is returned in the response
    Affected if Protected content is returned without authentication being validated

If the Slider Revolution plugin is installed and the get_stream_data endpoint returns password-protected content to unauthenticated users, the environment is affected by this vulnerability.

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 plugin to a version newer than 7.0.9. If immediate update is not possible, restrict access to the vulnerable endpoint via web server configuration or disable the plugin until patching is feasible.

Recommended fix Moderate confidence

Latest available version of Slider Revolution (any version newer than 7.0.9)

  1. 1. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  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. After updating, verify the plugin version is newer than 7.0.9
  5. 5. Confirm the vulnerability is resolved by testing that unauthenticated access to password-protected content is no longer possible
Caveat Minor: Standard precautions apply when updating any WordPress plugin (backup site before updating)

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

Have this fixed 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 help mitigating

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-2026-6728 — 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-6728 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