dbcve.org
ListingproWordPress extension · Cridio

CVE-2024-39624

HIGH · 8.8 CVSS v3.1 Published 2024-08-01
Fix available
A fix is available. Upgrade to 2.9.5 or later.
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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in CridioStudio ListingPro listingpro allows PHP Local File Inclusion.This issue affects ListingPro: from n/a through <= 2.9.4.

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 ListingPro WordPress plugin versions up to 2.9.4 contains a path traversal vulnerability that allows PHP Local File Inclusion (LFI). Attackers can manipulate file path parameters to access files outside the intended restricted directory, potentially exposing sensitive system files, configuration files, or other application data.

MitigationImplement strict input validation using realpath() to resolve canonical paths and verify they fall within allowed directories; employ whitelist-based file inclusion logic and disable potentially dangerous PHP includes unless absolutely necessary.

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
ListingproWordPress extension
Affected:< 2.9.5

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 if ListingPro plugin is installed
    Locate the ListingPro plugin in your WordPress installation at wp-content/plugins/ or check via WordPress admin under Plugins > Installed Plugins
    Affected if The ListingPro plugin by Cridio appears in your plugins list
  2. Determine installed plugin version
    Open the main plugin file (typically plugin-name.php in the plugin directory) and locate the version comment/constant, or check the version displayed in WordPress admin plugins page
    Affected if The reported version number is lower than 2.9.5 (e.g., 2.9.4, 2.8.x, etc.)
  3. Locate file inclusion code in plugin files
    Search plugin PHP files for dynamic include/require statements that use variables or request parameters (e.g., include($_GET['file'], include($path, require_once with user-supplied data)
    Affected if Files contain include/require statements using unsanitized variables from $_GET, $_POST, or $_REQUEST
  4. Identify exposed file path parameters
    Test plugin AJAX endpoints or pages that accept file path parameters by manipulating the parameter values with directory traversal sequences like ../../
    Affected if The plugin accepts and processes path parameters that allow traversing outside the intended directory
  5. Check for unauthorized file access attempts
    Review web server access logs for patterns like ../ or ../../ in requests to ListingPro plugin endpoints, looking for suspicious path traversal attempts
    Affected if Logs show traversal attempts targeting ListingPro endpoints or unexpected file paths being requested

Your environment is affected if the Cridio ListingPro plugin version is below 2.9.5 AND the plugin's file inclusion functionality is exposed through accessible endpoints that accept user-supplied path 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
Upgrade available Upgrade to 2.9.5 or later
Fixed in 2.9.5
Interim mitigation

Implement strict input validation using realpath() to resolve canonical paths and verify they fall within allowed directories; employ whitelist-based file inclusion logic and disable potentially dangerous PHP includes unless absolutely necessary.

Recommended fix High confidence

ListingPro 2.9.5

  1. 1. Backup your current ListingPro installation and database before making any changes
  2. 2. Download ListingPro version 2.9.5 from the official source (ThemeForest or CridioStudio)
  3. 3. Upgrade the plugin/theme following the standard ListingPro update procedure
  4. 4. Verify the installation was successful
  5. 5. Test that the path traversal vulnerability is no longer exploitable

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

Fix this in Listingpro Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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