dbcve.org
ListingproWordPress extension · Cridio

CVE-2024-39621

HIGH · 7.2 CVSS v3.1 Published 2024-08-01
Fix available
A fix is available. Upgrade to 2.9.5 or later.
See remediation →
78/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 CridioStudio ListingPro listingpro-plugin 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 has a path traversal vulnerability allowing local file inclusion. Attackers can use directory traversal sequences (../) in user-controlled input to include arbitrary PHP files from the server, potentially achieving remote code execution.

MitigationUpdate ListingPro to the latest patched version. If no patch is available, disable the plugin or implement web application firewall rules to block directory traversal patterns in request parameters.

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Check if ListingPro plugin is installed
    Navigate to WordPress admin dashboard > Plugins, or inspect wp-content/plugins/listingpro directory, or query the WordPress database plugins table
    Affected if The ListingPro plugin by Cridio is present on the WordPress site
  2. Determine installed ListingPro version
    Check the plugin header in its main PHP file (typically wp-content/plugins/listingpro/listingpro.php) for the Version field, or view the version in WordPress Plugins admin panel
    Affected if The version displayed is lower than 2.9.5 or the version field cannot be read (indicating an unpatched or very old install)
  3. Verify the plugin is active
    Check WordPress admin > Plugins > Active Plugins list, or query wp_options table for option_name = 'active_plugins'
    Affected if ListingPro appears in the active plugins list and version is < 2.9.5
  4. Inspect HTTP requests for suspicious traversal patterns
    Review web server access logs (Apache/nginx) for requests containing '../' patterns targeting ListingPro endpoints, or monitor live traffic for parameters with directory traversal sequences
    Affected if Requests containing ../ patterns are observed in logs targeting ListingPro-related URLs
  5. Check for unexpected PHP file inclusions
    Examine the plugin code for include/require statements using user-supplied parameters without proper sanitization, particularly in ajax handlers or template files
    Affected if Code review reveals include/require calls using $_GET or $_POST parameters without sanitization preventing directory traversal

If the ListingPro plugin is installed, active, and its version is lower than 2.9.5, the environment is vulnerable to CVE-2024-39621 path traversal exploitation.

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

Update ListingPro to the latest patched version. If no patch is available, disable the plugin or implement web application firewall rules to block directory traversal patterns in request parameters.

Recommended fix Moderate confidence

ListingPro version 2.9.5

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the ListingPro plugin in the list
  4. 4. If an update is available, click 'Update Now' to update to version 2.9.5
  5. 5. Alternatively, download ListingPro version 2.9.5 from a trusted source and upload it via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is running version 2.9.5 under Plugins > Installed Plugins

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-39621 — 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-39621 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