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

CVE-2024-52386

MEDIUM · 5.3 CVSS v3.1 Published 2024-11-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/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 Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in RadiusTheme Classified Listing classified-listing allows PHP Local File Inclusion.This issue affects Classified Listing: from n/a through <= 3.1.16.

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

A PHP Local File Inclusion (LFI) vulnerability in the RadiusTheme Classified Listing WordPress plugin (versions <=3.1.16) allows attackers to include arbitrary PHP files from the server file system due to improper control of filenames in include/require statements, potentially leading to remote code execution.

MitigationUpdate the Classified Listing plugin to the latest version beyond 3.1.16. If no patched version is available, temporarily disable the plugin and review server file permissions to restrict web user access to sensitive files.

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

CVSS:3.1/AV:N/AC:H/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. Locate the Classified Listing plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and find 'Classified Listing' by RadiusTheme, or check the plugin files in wp-content/plugins/classified-listing/ for a version file or readme.txt containing the version number
    Affected if The plugin is not found in the WordPress installation
  2. Identify the installed plugin version
    Open the plugin's main file (usually class-listing.php or similar) or the readme.txt file within the classified-listing plugin directory and locate the Version: field
    Affected if The version number cannot be determined or the plugin file is missing
  3. Compare the version against the affected range
    Compare your installed version number to 3.1.16 - if your version is 3.1.16 or lower (such as 3.1.15, 3.1.0, etc.), you are within the affected range
    Affected if Your installed version is 3.1.16 or lower
  4. Inspect the plugin for vulnerable include/require statements
    Search the plugin PHP files for include, require, include_once, or require_once statements that use unsanitized variables in the path (look for patterns like include($variable or require $_GET/$_POST without validation)
    Affected if Such insecure file inclusion code patterns exist in the plugin

You are affected if the Classified Listing plugin by RadiusTheme is installed at version 3.1.16 or lower and contains the vulnerable file inclusion code pattern.

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

Update the Classified Listing plugin to the latest version beyond 3.1.16. If no patched version is available, temporarily disable the plugin and review server file permissions to restrict web user access to sensitive files.

Recommended fix Moderate confidence

Latest version of Classified Listing plugin (version > 3.1.16)

  1. Identify the currently installed version of the RadiusTheme Classified Listing plugin in your WordPress installation
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Check if a newer version of the Classified Listing plugin is available in the WordPress plugin repository
  4. If a newer version (greater than 3.1.16) is available, update the plugin to the latest version
  5. After updating, verify the plugin version number reflects the update
  6. Test critical functionality of the classified listing feature to ensure the update did not break existing features
  7. Review plugin changelog or security advisories from RadiusTheme or Patchstack for any additional required actions
Caveat Minor or patch updates typically have low breaking change risk; review changelog before updating

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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