dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-64377

HIGH · 8.1 CVSS v3.1 Published 2025-12-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in CridioStudio ListingPro listingpro allows PHP Local File Inclusion.This issue affects ListingPro: from n/a through < 2.9.10.

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

CridioStudio ListingPro contains a PHP Local File Inclusion (LFI) vulnerability where user-supplied input is not properly validated before being used in include/require statements. This allows attackers to include arbitrary local files, potentially leading to remote code execution if they can upload files or access sensitive system files.

MitigationUpgrade to ListingPro version 2.9.10 or later. Additionally, implement strict input validation using allowlists for any user-controlled input used in file inclusion operations, and ensure PHP's allow_url_include setting is disabled.

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

CVSS:3.1/AV:N/AC:H/PR:N/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. Confirm ListingPro installation
    Identify if the CridioStudio ListingPro theme or plugin is present in your WordPress environment. Check the wp-content/themes or wp-content/plugins directory for a ListingPro folder.
    Affected if ListingPro is installed in the WordPress environment
  2. Check installed version
    Locate the version number for ListingPro. This is typically found in the style.css header (for themes), readme.txt, or the main plugin file. Compare it to version 2.9.10.
    Affected if The installed version is lower than 2.9.10
  3. Search for file inclusion with user input
    Examine the ListingPro source code for patterns where include(), require(), include_once(), or require_once() use variables directly without validation. Focus on files that process URL parameters ($_GET, $_POST, $_REQUEST) as part of the file path.
    Affected if Code patterns exist where user-supplied input is used directly in include/require statements without sanitization
  4. Identify accessible file inclusion points
    Determine if any vulnerable file inclusion code can be reached via HTTP requests. Check if URL parameters that control file paths are exposed and can be manipulated by unauthenticated users.
    Affected if User-controllable parameters in file inclusion code are accessible via web requests without authentication

If ListingPro is present with a version below 2.9.10 and contains code that passes user input directly to PHP include/require functions, the environment is affected by this LFI vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to ListingPro version 2.9.10 or later. Additionally, implement strict input validation using allowlists for any user-controlled input used in file inclusion operations, and ensure PHP's allow_url_include setting is disabled.

Recommended fix High confidence

ListingPro version 2.9.10 or later

  1. Create a complete backup of your WordPress site (files and database) before proceeding
  2. Log in to your WordPress admin dashboard
  3. Navigate to Appearance > Themes (if it's a theme) or Plugins (if it's a plugin)
  4. Locate the ListingPro theme/plugin in the list
  5. Click the Update button to update to the latest version, or manually upload version 2.9.10 or higher if automatic update is not available
  6. Verify the update was successful by checking the installed version
  7. Clear any cache if you use caching plugins
  8. Test critical functionality of the listing site to ensure nothing broke

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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