dbcve.org
Sp Project \& Document ManagerWordPress extension · Smartypantsplugins

CVE-2024-37224

MEDIUM · 6.5 CVSS v3.1 Published 2024-07-09
Fix available
A fix is available. Upgrade to after 4.71 or later.
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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in smartypants SP Project & Document Manager.This issue affects SP Project & Document Manager: from n/a through 4.71.

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

Path traversal vulnerability in SP Project & Document Manager allows attackers to access files outside restricted directories using directory traversal sequences (e.g., ../../../'). The vulnerability exists in file handling operations within the plugin.

MitigationImplement strict input validation on all file path parameters to ensure paths resolve within allowed directories, use realpath() to canonicalize paths and verify they remain within intended boundaries, and apply principle of least privilege to file access operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sp Project \& Document ManagerWordPress extension
Affected:<= 4.71

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 plugin installation and version
    Locate the SP Project & Document Manager plugin in your WordPress installation (typically in wp-content/plugins/sp-client-document-manager/) and check the main plugin file (usually sp-client-document-manager.php or similar) for the version declaration. In WordPress admin, go to Plugins > Installed Plugins and look for 'SP Project & Document Manager' to see the current version number.
    Affected if The installed version is 4.71 or lower (any version <= 4.71 is affected)
  2. Identify if file management features are active
    Check if the plugin's file upload, download, or document management features are enabled. Look for plugin settings in WordPress admin under 'SP Project & Document Manager' menu items. Verify if any file handling modules (upload, download, preview, or client access features) are configured and accessible.
    Affected if File handling or document management features are enabled and accessible to users
  3. Check for exposed file handling endpoints
    Review the plugin's PHP files for functions that handle file paths (search for $_GET, $_POST, or $_REQUEST parameters used in file operations like fopen, file_get_contents, include, require, or similar file functions). Common patterns include parameters named 'file', 'path', 'doc', 'download', or 'folder' that accept user input.
    Affected if The plugin processes user-supplied file paths without strict validation (the vulnerability condition)
  4. Verify web server access to sensitive directories
    Confirm that the web server process has read access to directories outside the intended upload/workspace folder (e.g., parent directories, wp-content, wp-config.php, or other system directories). This is determined by file system permissions, not plugin configuration.
    Affected if The web server user can read files outside the intended plugin directory

You are affected if SP Project & Document Manager version 4.71 or lower is installed AND the file management features are enabled, allowing unauthenticated or low-privilege users to manipulate file paths in file handling operations.

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
Upgrade available Upgrade to a release after 4.71
Interim mitigation

Implement strict input validation on all file path parameters to ensure paths resolve within allowed directories, use realpath() to canonicalize paths and verify they remain within intended boundaries, and apply principle of least privilege to file access operations.

Fix this in Sp Project \& Document Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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