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

CVE-2025-39387

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 wpoperations Opstore opstore allows PHP Local File Inclusion.This issue affects Opstore: from n/a through <= 1.4.5.

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 vulnerability in wpoperations Opstore plugin allows attackers to include arbitrary local PHP files through unsanitized user input in include/require statements, potentially leading to remote code execution.

MitigationImplement strict input validation and allowlisting for file inclusion paths, avoiding direct use of user-supplied input in include/require statements; upgrade to 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 Opstore plugin is installed
    Access WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'wpoperations Opstore' or 'Opstore' in the list. Note the installed version if displayed.
    Affected if The Opstore plugin by wpoperations is present and active on the WordPress site
  2. Identify file inclusion endpoints
    Search plugin source code for 'include(', 'require(', 'include_once(', or 'require_once(' statements that use variables (e.g., $_GET, $_POST, $_REQUEST) directly without sanitization. Common vulnerable patterns: include($_GET['file']); or require($path . $_REQUEST['page']);
    Affected if Code contains include/require statements using raw user-supplied input without validation or allowlisting
  3. Check web-accessible file inclusion parameters
    Review the plugin's PHP files for parameters that accept file paths and are accessible via HTTP requests (typically in the query string). Common parameter names: 'page', 'file', 'path', 'load', 'include'. Test by attempting to include a known local file like '../../../../wp-config.php'
    Affected if URL parameters controllable by an attacker are used in file inclusion operations without sanitization
  4. Verify authentication requirements
    Check if the vulnerable file inclusion code is wrapped behind authentication checks (e.g., current_user_can(), is_admin(), check_admin_referer()). Review the function containing the include/require to see if it runs before any access control.
    Affected if The file inclusion functionality is accessible to unauthenticated users or users without proper privileges
  5. Compare installed version to patched version
    If the plugin displays version information, compare it to any available patched version from the plugin developer or security advisory. If no patched version is known, treat any version as potentially affected.
    Affected if Installed version lacks security patches for the LFI vulnerability or no patched version information is available

The environment is affected if the wpoperations Opstore plugin is installed, the version contains the LFI vulnerability, and the file inclusion functionality is accessible without proper input sanitization or authentication.

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

Implement strict input validation and allowlisting for file inclusion paths, avoiding direct use of user-supplied input in include/require statements; upgrade to patched version if available.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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