CVE-2025-31040
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Exthemes WP Food ordering and Restaurant Menu wp-food allows PHP Local File Inclusion.This issue affects WP Food ordering and Restaurant Menu: from n/a through <= 2.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 confidenceA PHP Local File Inclusion vulnerability exists in the Exthemes WP Food ordering and Restaurant Menu plugin (wp-food) for WordPress versions through 2.7. The vulnerability stems from improper control of filename parameters in include/require statements, allowing attackers to include arbitrary local files. This could enable reading sensitive files or, when chained with other techniques, potentially achieve remote code execution.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm wp-food plugin is installedLog in to WordPress admin panel and navigate to Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'wp-food' or similar variantAffected if The wp-food plugin folder exists in the WordPress plugins directory
-
Identify installed plugin versionCheck the plugin header in the main PHP file (typically wp-content/plugins/wp-food/wp-food.php or similar) for the 'Version' comment, or view the version in the WordPress plugin repository pageAffected if The installed version is 2.7 or lower (the affected range is through version 2.7)
-
Locate file inclusion code patternsSearch plugin PHP files for include, require, include_once, or require_once statements that use variable parameters without proper sanitization (e.g., include($file), require($_GET['page']) )Affected if Unsanitized file inclusion calls are present that accept user-controlled input
-
Identify accessible entry pointsExamine the plugin's AJAX handlers (admin-ajax.php?action=...) or direct PHP files that may accept filename parameters via GET/POST requestsAffected if URL parameters controlling file inclusion are accessible without authentication or with low-privileged user access
-
Test for local file inclusion capabilityIf accessible, attempt a benign local file inclusion request using a known safe file path (e.g., ../../wp-config.php or /etc/passwd) to confirm the vulnerability existsAffected if The application returns content from files outside the intended plugin directory
A user is affected if the wp-food plugin version is 2.7 or lower and the vulnerable file inclusion functionality is accessible, allowing arbitrary local file reads.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the wp-food plugin to the latest patched version immediately. If no patched version is available, disable the plugin and implement a Web Application Firewall (WAF) as an interim measure to block malicious file inclusion requests.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2025-31040 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-31040 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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