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

CVE-2025-52715

HIGH · 7.5 CVSS v3.1 Published 2025-06-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/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 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 <= 4.2.0.

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

Local File Inclusion (LFI) vulnerability in the RadiusTheme Classified Listing WordPress plugin allows attackers to include arbitrary PHP files from the server filesystem via improper input validation in include/require statements. This can lead to exposure of sensitive files or potentially remote code execution if attacker-controlled files exist on the server.

MitigationUpdate Classified Listing plugin to the latest patched version as soon as available. Until patched, consider deploying WAF rules to block directory traversal patterns (e.g., ../, ..\) or restricting file inclusion functions in PHP configuration.

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
High
Availability
High

CVSS:3.1/AV:N/AC:H/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. Confirm Classified Listing plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, or inspect the /wp-content/plugins/classified-listing/ directory via file manager/SSH
    Affected if The Classified Listing plugin by RadiusTheme is present on the WordPress site
  2. Identify installed plugin version
    Check the plugin header in /wp-content/plugins/classified-listing/classified-listing.php for the Version field, or view the version in the WordPress plugins admin UI
    Affected if A version of Classified Listing is installed and can be compared to the patched version
  3. Locate the vulnerable file inclusion code
    Search plugin source files for include/require statements that use unsanitized variables, such as: include($_GET['file']) or require_once($some_variable), typically in files handling template or file path parameters
    Affected if The plugin contains include/require statements using request parameters without proper validation (e.g., no realpath() check, no allowlist)

You are affected if the Classified Listing plugin is installed and its file inclusion code uses unsanitized input from include/require statements, allowing directory traversal to read arbitrary PHP files on the server.

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 Classified Listing plugin to the latest patched version as soon as available. Until patched, consider deploying WAF rules to block directory traversal patterns (e.g., ../, ..\) or restricting file inclusion functions in PHP configuration.

Recommended fix Moderate confidence

Latest version of Classified Listing plugin (version greater than 4.2.0)

  1. Check the current version of the Classified Listing plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the Classified Listing plugin by RadiusTheme
  4. If your current version is 4.2.0 or below, update to the latest available version from the WordPress plugin repository
  5. After updating, verify the plugin functions correctly on your site
  6. Check the plugin changelog or release notes to confirm the security fix for the Local File Inclusion vulnerability is included in the version you upgraded to
Caveat Review plugin settings and test classified listing functionality after upgrade to ensure compatibility with your theme and other plugins

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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