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

CVE-2025-69387

HIGH · 7.5 CVSS v3.1 Published 2026-02-20
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 whatwouldjessedo Simple Retail Menus simple-retail-menus allows PHP Local File Inclusion.This issue affects Simple Retail Menus: from n/a through <= 4.2.1.

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 Simple Retail Menus plugin (versions up to 4.2.1) allows attackers to include arbitrary local PHP files via improper control of a filename parameter in include/require statements. This occurs when user-supplied input is used directly in file inclusion functions without proper validation or sanitization.

MitigationImplement strict input validation using an allowlist approach for any parameters used in include/require statements, or avoid using user input entirely in file inclusion functions. If file inclusion functionality is required, use a whitelist of permitted files and ensure path traversal sequences are blocked.

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. Identify if Simple Retail Menus plugin is installed
    Check the WordPress plugins directory or plugin registry for 'simple-retail-menus' or 'Simple Retail Menus'
    Affected if Plugin is present in the WordPress installation
  2. Determine the installed plugin version
    Inspect the plugin header file (typically main PHP file or readme.txt) for the 'Version' field
    Affected if Version is 4.2.1 or lower
  3. Locate PHP files using include/require with dynamic variables
    Search plugin directory for patterns like 'include($_', 'require($_', 'include($', 'require($' without sanitization
    Affected if File inclusion code uses raw user input variables without validation
  4. Check for vulnerable parameter handling
    Review code for parameters passed to include/require statements, looking for direct use of $_GET, $_POST, or similar superglobals
    Affected if User-supplied parameters flow directly to include/require without sanitization
  5. Verify the attack surface is exposed
    Test whether the affected parameter is accessible via HTTP requests (GET/POST) without authentication requirements
    Affected if The vulnerable file inclusion endpoint is accessible to unauthenticated or low-privilege users

The environment is affected if Simple Retail Menus plugin version 4.2.1 or lower is installed AND the vulnerable code pattern using unsanitized user input in include/require statements exists and is accessible.

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

Implement strict input validation using an allowlist approach for any parameters used in include/require statements, or avoid using user input entirely in file inclusion functions. If file inclusion functionality is required, use a whitelist of permitted files and ensure path traversal sequences are blocked.

Recommended fix Moderate confidence

Simple Retail Menus version 4.2.2 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Simple Retail Menus' plugin by whatwouldjessedo
  4. 4. Check the current installed version (should be <= 4.2.1)
  5. 5. Click 'Update Now' if version 4.2.2 or later is available, or manually download and upload version 4.2.2 or later from a trusted source
  6. 6. After update, verify the plugin is running version 4.2.2 or newer

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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