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

CVE-2025-39384

HIGH · 7.5 CVSS v3.1 Published 2025-04-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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 cedcommerce Product Lister for eBay product-lister-ebay allows PHP Local File Inclusion.This issue affects Product Lister for eBay: from n/a through <= 2.0.9.

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

This is a PHP Local File Inclusion (LFI) vulnerability in the cedcommerce Product Lister for eBay plugin (versions up to 2.0.9). The vulnerability allows attackers to read sensitive local files from the server due to improper control of filenames in PHP include/require statements, enabling path traversal attacks.

MitigationRemediate by implementing strict input validation and sanitization on all file path parameters used in include/require statements, using allowlists or resolving paths canonically before inclusion. Update to a patched version if available.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 the cedcommerce Product Lister for eBay plugin is installed
    Access the WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'cedcommerce Product Lister for eBay' in the list. Alternatively, check the filesystem at wp-content/plugins/ for a directory named 'cedcommerce-ebay-product-lister' or similar.
    Affected if The plugin is present in the WordPress installation
  2. Determine the installed plugin version
    In the WordPress admin panel, click on the plugin name to view its details and locate the version number. Alternatively, check the main plugin PHP file header in the plugin directory for the 'Version' tag.
    Affected if The version is 2.0.9 or lower (the affected range includes versions up to 2.0.9)
  3. Identify PHP files using dynamic include/require statements
    Search the plugin directory for PHP files containing include, include_once, require, or require_once statements where the file path comes from a variable (e.g., include($file), require($_GET['path']), include_once($path)). Use grep or a code editor to search for patterns like 'include\$' or 'require\$' in the plugin folder.
    Affected if Dynamic file inclusion with user-controlled input is present in the plugin code
  4. Inspect file path parameters for path traversal vulnerabilities
    Examine the identified include/require statements to determine if path parameters can accept directory traversal sequences like '../' or absolute file paths via HTTP request parameters (commonly 'file', 'path', 'page', 'template', or similar). Test by attempting to include a known file using a parameter like ?file=../../../../etc/passwd (if parameter exists).
    Affected if The file path parameters in include/require statements accept traversal sequences without validation
  5. Verify web accessibility of vulnerable endpoints
    Check if the PHP files containing the vulnerable include/require logic are accessible via HTTP requests without authentication. Attempt to access the suspected endpoint directly through the browser with a test path traversal parameter.
    Affected if The vulnerable file inclusion logic is reachable via unauthenticated HTTP requests

A user is affected if the cedcommerce Product Lister for eBay plugin is installed with version 2.0.9 or lower and contains PHP files with dynamic include/require statements that accept unsanitized file path parameters accessible via web requests.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Remediate by implementing strict input validation and sanitization on all file path parameters used in include/require statements, using allowlists or resolving paths canonically before inclusion. Update to a patched version if available.

Have this fixed 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 help mitigating

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-2025-39384 — 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-39384 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