Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-31040: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in Exthemes WP Food ordering and Restaurant Menu

0
Unknown
VulnerabilityCVE-2025-31040cvecve-2025-31040
Published: Fri Apr 11 2025 (04/11/2025, 08:42:49 UTC)
Source: CVE Database V5
Vendor/Project: Exthemes
Product: WP Food ordering and Restaurant Menu

Description

Improper 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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/02/2026, 00:56:28 UTC

Technical Analysis

CVE-2025-31040 is a vulnerability identified in the Exthemes WP Food ordering and Restaurant Menu WordPress plugin, affecting versions up to and including 2.7. The issue stems from improper control over the filename parameter used in PHP include or require statements, which leads to a Local File Inclusion (LFI) vulnerability. LFI vulnerabilities occur when an attacker can manipulate input to include files from the local filesystem, potentially exposing sensitive information such as configuration files, password files, or application source code. In some cases, LFI can be leveraged to achieve remote code execution if combined with other vulnerabilities or misconfigurations. This vulnerability does not require authentication or user interaction, increasing its risk profile. Although no known exploits are currently reported in the wild, the widespread use of WordPress and the popularity of food ordering plugins make this a significant concern. The vulnerability was reserved in late March 2025 and published in April 2025, but no CVSS score has been assigned yet. The lack of patch links suggests that a fix may not have been released at the time of reporting. Attackers exploiting this flaw could gain unauthorized access to sensitive files or execute arbitrary PHP code, compromising the confidentiality, integrity, and availability of affected systems.

Potential Impact

The potential impact of CVE-2025-31040 is substantial for organizations running WordPress sites with the vulnerable WP Food ordering and Restaurant Menu plugin. Successful exploitation can lead to unauthorized disclosure of sensitive files such as database credentials, configuration files, or user data, resulting in confidentiality breaches. Additionally, attackers may execute arbitrary code on the server, leading to full system compromise, data manipulation, or service disruption. This can damage organizational reputation, lead to financial losses, and cause regulatory compliance issues, especially for businesses in the food service sector handling customer data. Since the vulnerability does not require authentication, any attacker with network access to the vulnerable site can attempt exploitation, increasing the attack surface. The absence of known exploits currently limits immediate widespread impact, but the risk remains high due to the ease of exploitation and the critical nature of the vulnerability.

Mitigation Recommendations

To mitigate CVE-2025-31040, organizations should first verify if they are using the Exthemes WP Food ordering and Restaurant Menu plugin version 2.7 or earlier. Immediate steps include: 1) Monitoring official Exthemes channels and WordPress plugin repositories for patches or updates addressing this vulnerability and applying them promptly. 2) If no patch is available, manually review and harden the plugin code by implementing strict input validation and sanitization on any parameters used in include or require statements to prevent arbitrary file inclusion. 3) Employ Web Application Firewalls (WAFs) with rules designed to detect and block attempts to exploit LFI vulnerabilities, such as suspicious file path traversal patterns. 4) Restrict file permissions on the web server to limit access to sensitive files and directories, minimizing the impact of potential file inclusion. 5) Conduct regular security audits and vulnerability scans on WordPress installations to detect vulnerable plugins and misconfigurations. 6) Educate site administrators about the risks of installing unverified plugins and the importance of timely updates. These targeted actions go beyond generic advice by focusing on the specific nature of the vulnerability and the plugin involved.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2025-03-26T09:23:26.402Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69cd7340e6bfc5ba1def1468

Added to database: 4/1/2026, 7:34:24 PM

Last enriched: 4/2/2026, 12:56:28 AM

Last updated: 4/6/2026, 9:38:34 AM

Views: 4

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses