dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-44034

HIGH · 7.5 CVSS v3.1 Published 2024-10-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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 Martin Greenwood WPSPX wpspx allows PHP Local File Inclusion.This issue affects WPSPX: from n/a through <= 1.0.2.

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 WPSPX allows attackers to manipulate file path inputs to include arbitrary PHP files from the local system, potentially leading to remote code execution through malicious PHP inclusion.

MitigationUpgrade to a patched version of WPSPX or implement strict input validation with allowlist filtering to prevent directory traversal sequences in file inclusion requests.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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. Verify WPSPX plugin is installed and active
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WPSPX' or search for it. Check if it shows as 'Active'. Alternatively, check the filesystem for the presence of /wp-content/plugins/wpspx/ directory.
    Affected if WPSPX is installed and active in WordPress
  2. Determine installed WPSPX version
    In WordPress admin, go to Plugins > Installed Plugins > WPSPX and read the version number from the plugin details. Alternatively, check the main plugin file header in /wp-content/plugins/wpspx/wpspx.php for the 'Version' field.
    Affected if The installed version does not match the patched version released after CVE-2024-44034 (compare your version to vendor release notes)
  3. Identify if file inclusion endpoints are accessible
    Search WPSPX source code for functions that handle file inclusion or require/include statements with user-controlled input. Look for parameters like 'file', 'path', 'template', or 'page' in the codebase. Check for any publicly accessible AJAX handlers or front-end endpoints.
    Affected if WPSPX contains file inclusion functionality that processes user-supplied path parameters without proper validation
  4. Inspect file inclusion parameters in HTTP traffic
    Review web server access logs and WPSPX-specific logs for requests containing directory traversal sequences such as '../', '..\', or absolute paths in parameters that might control file inclusion. Example: grep for '..' in access logs for requests to WPSPX-related URLs.
    Affected if Requests to WPSPX contain traversal sequences like '../' in file-related parameters and these are processed by the application
  5. Check for unauthorized PHP file inclusions
    Examine WPSPX includes/require statements in PHP files to verify they use allowlist validation or basename/realpath functions. Look for code patterns like 'include($_GET[file])' or similar unsanitized input usage.
    Affected if WPSPX code includes files using raw user input without validation through functions like basename(), realpath(), or allowlist checking

Your environment is affected if WPSPX is installed and active with an unpatched version that contains file inclusion functionality accessible to users without proper path traversal validation.

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

Upgrade to a patched version of WPSPX or implement strict input validation with allowlist filtering to prevent directory traversal sequences in file inclusion requests.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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