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

CVE-2025-26933

HIGH · 7.5 CVSS v3.1 Published 2025-03-10
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 Nitin Prakash WC Place Order Without Payment wc-place-order-without-payment allows PHP Local File Inclusion.This issue affects WC Place Order Without Payment: from n/a through <= 2.6.7.

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

The WC Place Order Without Payment WordPress plugin versions 2.6.7 and below contain a PHP Local File Inclusion vulnerability. This stems from improper control of filenames in include/require statements, likely due to unsanitized user input being used to construct file paths. An attacker could exploit this to include arbitrary PHP files from the server, potentially executing malicious code.

MitigationUpdate the plugin to the latest version if a patch is available; otherwise, disable the plugin until a fix is released. Additionally, ensure PHP's allow_url_include is disabled and review code for unsanitized input in include/require operations.

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. Verify the plugin is installed
    Navigate to WordPress admin > Plugins and look for 'WC Place Order Without Payment' in the list of installed plugins, or inspect the /wp-content/plugins/ directory for a folder containing 'place-order-without-payment' in the name
    Affected if The plugin is not found in the installed plugins list or directory
  2. Check the installed plugin version
    In WordPress admin > Plugins, click on the plugin name to view its details and find the version number, or open the main plugin PHP file (usually in wp-content/plugins/place-order-without-payment/) and look for the 'Version' header in the plugin comment block
    Affected if The version number displayed is 2.6.7 or lower
  3. Confirm the plugin is active
    In WordPress admin > Plugins, check the status column for the plugin; an 'Active' status means the plugin code is currently loaded and executing
    Affected if The plugin shows as Active rather than Inactive or Deactivated
  4. Identify potential LFI entry points
    Review the plugin PHP files, particularly any that handle include or require statements with variables that could originate from user input (such as $_GET, $_POST, or $_REQUEST parameters); search for patterns like 'include($', 'require($', 'include_once($', or 'require_once($' followed by variables
    Affected if The plugin code contains include/require statements using unsanitized user-supplied variables in the file path
  5. Check PHP configuration for allow_url_include
    Create a PHP info page or check the php.ini file for the 'allow_url_include' directive setting
    Affected if allow_url_include is enabled (set to On), which would allow inclusion of remote files in addition to local files, increasing exploit severity

You are affected if the WC Place Order Without Payment plugin is installed at version 2.6.7 or below and is currently active, with the vulnerability requiring the plugin to process unsanitized user input through include/require statements.

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

Update the plugin to the latest version if a patch is available; otherwise, disable the plugin until a fix is released. Additionally, ensure PHP's allow_url_include is disabled and review code for unsanitized input in include/require operations.

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-26933 — 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-26933 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