dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-6692

HIGH · 8.8 CVSS v3.1 Published 2026-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Arbitrary File Upload in versions 7.0.0 to 7.0.10 via the '_get_media_url' and '_check_file_path' function. This is due to insufficient file type validation. This makes it possible for authenticated attackers, with subscriber-level access and above, to upload files that may be executable, which makes remote code execution possible. The vulnerability was partially patched in version 7.0.10 and fully patched in version 7.0.11.

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 7.0.0 through 7.0.10 is vulnerable to arbitrary file upload due to insufficient file type validation in the '_get_media_url' and '_check_file_path' functions. Authenticated attackers with subscriber-level access or higher can upload executable files, enabling remote code execution.

MitigationUpdate Slider Revolution plugin to version 7.0.11 or later to apply the complete patch. If immediate update is not possible, restrict or disable file upload functionality for lower-privileged users until the patch can be applied.

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

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

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 installation and version
    In WordPress admin, go to Plugins > Installed Plugins > Slider Revolution and note the version number displayed, or query the WordPress database plugins table for the plugin version.
    Affected if The installed version is 7.0.0 through 7.0.10 inclusive.
  2. Confirm plugin is active
    Verify that the Slider Revolution plugin shows as 'Active' in the WordPress plugins list.
    Affected if The plugin is installed and currently active.
  3. Check for subscriber-level user accounts
    In WordPress admin, go to Users and review the list for any accounts assigned the 'Subscriber' role, or query the wp_usermeta table where meta_key = 'wp_capabilities' and meta_value contains 'subscriber'.
    Affected if At least one user account with subscriber-level access exists.
  4. Verify file upload endpoint accessibility
    Test access to the plugin's media upload functionality by submitting a request to the endpoint handling the '_get_media_url' or '_check_file_path' functions, or check if the plugin's upload handlers are reachable via the WP REST API or admin-ajax.
    Affected if The upload endpoints are accessible without higher privileges.

A user is affected if they have Slider Revolution plugin version 7.0.0-7.0.10 installed and active with at least one subscriber-level account and the upload functionality is accessible to that role.

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 version 7.0.11 or later to apply the complete patch. If immediate update is not possible, restrict or disable file upload functionality for lower-privileged users until the patch can be applied.

Recommended fix High confidence

Slider Revolution version 7.0.11 or later

  1. 1. Back up your WordPress site (database and files) before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the Slider Revolution plugin in the list
  4. 4. Click 'Update now' if an update is available, or manually upload version 7.0.11 or later from the WordPress plugin repository
  5. 5. Verify the plugin version after update to confirm version 7.0.11 or newer is installed
  6. 6. Test that the Slider Revolution functionality works correctly on your site
  7. 7. Monitor the site for any errors or unusual behavior

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

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

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