Is WP Food ordering and Restaurant Menu safe to use?

Laskyr does not give safety verdicts. WP Food ordering and Restaurant Menu is closed on wordpress.org. Closed on 2025-04-09 (reason given: Security Issue). Closed plugins get no updates through WordPress, so new security holes will not be fixed for you. Keep WP Food ordering and Restaurant Menu on the latest version and remove it if you do not use it.

Which versions of WP Food ordering and Restaurant Menu are vulnerable?

Known issues on record (newest first): Missing authorization check (2.7.1 and older, fixed in 2.7.1); File inclusion (2.7 and older). The full list with sources is on this page.

What should I do if my WP Food ordering and Restaurant Menu is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update wp-food). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · wp-food · data as of 2026-11-04

Is WP Food ordering and Restaurant Menu safe? Known vulnerabilities and latest version

Status: Closed 2025-04-09
Known issues on record: 2
Unpatched in latest: 0

What to do

Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.

With WP-CLI, once you have a replacement: wp plugin deactivate wp-food && wp plugin delete wp-food

Check your version

Known vulnerabilities

2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 2 record(s) do not state which versions are affected.

medium 5.3 CVE-2026-32440 · published 2026-03-13

Missing authorization check in WP Food ordering and Restaurant Menu (2.7.1 and older)

Affected: 2.7.1 and older
Fixed in: 2.7.1
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Missing Authorization vulnerability in Ex-Themes WP Food wp-food allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Food: from n/a through < 2.7.1.

NVD CVE-2026-32440 Patchstack advisory

high 8.1 CVE-2025-31040 · published 2025-04-11

File inclusion in WP Food ordering and Restaurant Menu (2.7 and older)

Affected: 2.7 and older
Fixed in: unknown
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

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.

NVD CVE-2025-31040 Patchstack advisory

Recent activity

2025-04-09 — closed on wordpress.org (Security Issue).
2026-03-13 — Missing authorization check disclosed (CVE-2026-32440), fixed in 2.7.1.
2025-04-11 — File inclusion disclosed (CVE-2025-31040), fix version not stated.

Free. We check the CVE feeds every day and email you only when a new issue for WP Food ordering and Restaurant Menu (wp-food) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Missing authorization (1) · File inclusion (1)

Where this data comes from

Version, last update, installs, closure: wordpress.org/plugins/wp-food (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/wp-food"><img src="https://laskyr.com/plugins/wp-food/badge.svg" alt="WP Food ordering and Restaurant Menu vulnerability status"></a>

← Check another plugin · Free hacked-site scan