Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-73400 – Unauthenticated Local File Inclusion – Restaurant Menu by MotoPress (mp-restaurant-

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-73400 is an unauthenticated Local File Inclusion (LFI) vulnerability in the Restaurant Menu by MotoPress WordPress plugin (mp-restaurant-menu), affecting all versions up to and including 2.4.11. The flaw allows a remote, unauthenticated attacker to force the plugin to include and execute arbitrary files on the server, with a CVSS v3.1 base score of 8.1 (High).

Technical details

  • Root cause: improper control of filename/path used in a PHP include/require statement (CWE-98), allowing attacker-influenced input to determine which file is loaded by the plugin.
  • Trigger conditions: no authentication or user interaction is required to reach the vulnerable code path.
  • Attack vector: network-based (remote HTTP request against the vulnerable WordPress site).
  • Impact: successful exploitation can lead to disclosure, modification, or destruction of server-side data, and depending on server configuration may enable arbitrary PHP code execution — reflected in high confidentiality, integrity, and availability impact ratings.

Affected software

  • Restaurant Menu by MotoPress (mp-restaurant-menu) WordPress plugin, versions up to and including 2.4.11.

Severity

  • CVSS v3.1 Base Score: 8.1 (High)
  • Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Update Restaurant Menu by MotoPress to the latest version released after 2.4.11, which addresses this issue.
  • If no patch can be applied immediately: disable or remove the plugin until it can be updated; restrict or monitor external access to the WordPress admin/plugin endpoints, and deploy a web application firewall rule to block path traversal/file-inclusion style payloads targeting the plugin.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body (HTML): /wp-content/plugins/mp-restaurant-menu/

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge