dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-9217

MEDIUM · 6.5 CVSS v3.1 Published 2025-08-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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 Path Traversal in all versions up to, and including, 6.7.36 via the 'used_svg' and 'used_images' parameters. This makes it possible for authenticated attackers, with Contributor-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information.

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.36 contain a path traversal vulnerability in the 'used_svg' and 'used_images' parameters. Authenticated attackers with Contributor-level access or higher can read arbitrary files on the server by manipulating these parameters to traverse the filesystem, potentially exposing sensitive configuration or system files.

MitigationUpdate Slider Revolution to version 6.7.37 or later to patch the path traversal vulnerability. Additionally, audit user accounts and restrict Contributor-level access to only trusted users, as this role can now exploit the vulnerability.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Confirm Slider Revolution plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Slider Revolution' in the list. Note if it is active or inactive.
    Affected if The plugin is installed and active on the WordPress site.
  2. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find Slider Revolution, and view the version number displayed beneath the plugin name. Alternatively, check the plugin's main PHP file header or the readme.txt file for the Version field.
    Affected if The installed version is 6.7.36 or lower.
  3. Verify Contributor or higher user roles exist
    In WordPress admin, go to Users > All Users and review the Role column. Identify any accounts assigned the Contributor role or higher (Author, Editor, Administrator).
    Affected if There is at least one user account with Contributor-level access or above.
  4. Check for exposure of used_svg and used_images endpoints
    Examine the site's HTTP traffic or source code for requests to endpoints containing 'used_svg' or 'used_images' parameters. These are typically found in AJAX calls or direct URL requests to the plugin's admin-ajax.php or custom endpoints.
    Affected if The site processes requests with these parameters, indicating the vulnerable functionality is reachable.

You are affected if Slider Revolution is installed at version 6.7.36 or below, the plugin is active, and there exists at least one user with Contributor-level access who could trigger the path traversal via the used_svg or used_images parameters.

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 6.7.37 or later to patch the path traversal vulnerability. Additionally, audit user accounts and restrict Contributor-level access to only trusted users, as this role can now exploit the vulnerability.

Recommended fix Moderate confidence

Slider Revolution version 6.7.37 or later (upgrade to latest available version)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Slider Revolution plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin version is above 6.7.36

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-2025-9217 — 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-2025-9217 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