dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-47351

HIGH · 7.5 CVSS v3.1 Published 2024-10-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in The CSSIgniter Team MaxSlider maxslider allows Path Traversal.This issue affects MaxSlider: from n/a through <= 1.2.3.

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 · moderate confidence

A path traversal vulnerability in the MaxSlider WordPress plugin allows attackers to manipulate file path parameters to access files outside the intended directory. The vulnerability exists in versions up to and including 1.2.3.

MitigationUpdate MaxSlider to the latest available version. If no update exists, implement strict input validation using realpath() and basename() to ensure file paths resolve within allowed directories, or restrict the plugin until a patch is released.

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

CVSS:3.1/AV:N/AC:H/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 MaxSlider plugin installation
    Check for the MaxSlider plugin directory in your WordPress installation at /wp-content/plugins/ or via WordPress admin under Plugins > Installed Plugins. Look for 'MaxSlider' in the plugin list.
    Affected if The MaxSlider plugin is present in the WordPress installation
  2. Determine installed version
    Open the plugin's main PHP file (typically maxslider.php) or the readme.txt file in the MaxSlider plugin directory and locate the version number in the plugin header comment.
    Affected if The version number displayed is 1.2.3 or lower (any version up to and including 1.2.3)
  3. Locate file path parameter functionality
    Review the MaxSlider plugin files for any features that accept file path parameters, such as image upload handlers, slider import/export functions, or custom file inclusion code. Search for $_GET, $_POST, or $_REQUEST variables used in file operations like include, require, file_get_contents, or similar.
    Affected if The plugin contains functionality that processes user-supplied file path parameters in file operations

You are affected if MaxSlider version 1.2.3 or lower is installed AND the plugin exposes file path parameter handling that can be manipulated for directory traversal.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update MaxSlider to the latest available version. If no update exists, implement strict input validation using realpath() and basename() to ensure file paths resolve within allowed directories, or restrict the plugin until a patch is released.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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