dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-40746

CRITICAL · 9.9 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Subscriber Arbitrary File Upload in Restaurant Zone <= 0.7.8 versions.

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 · moderate confidence

An arbitrary file upload vulnerability in the Restaurant Zone plugin/theme version 0.7.8 and below allows users with Subscriber-level privileges to upload arbitrary files, potentially enabling remote code execution.

MitigationUpdate Restaurant Zone to the latest patched version immediately. If no patch is available, disable subscriber registration or remove the plugin until a fix is released.

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
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 Restaurant Zone installation
    Check your WordPress plugins or themes directory for the Restaurant Zone plugin/theme folder. In WordPress admin, go to Plugins or Appearance > Themes to verify it is installed.
    Affected if Restaurant Zone plugin or theme is found on the system
  2. Determine installed version
    In WordPress admin, navigate to Plugins > Installed Plugins and find Restaurant Zone. Click on the plugin details to view the installed version number. Alternatively, check the style.css or main plugin file header for the Version field.
    Affected if The version is 0.7.8 or lower
  3. Verify subscriber role access
    In WordPress admin, go to Users > Users and check if any users have the Subscriber role. Go to Settings > General to see if "Anyone can register" is enabled and if the default role for new users is set to Subscriber.
    Affected if Subscriber role exists or anyone can register as Subscriber
  4. Check file upload capability
    Inspect the Restaurant Zone plugin code, specifically looking for file upload handlers, AJAX endpoints, or form handlers that accept file uploads. Search for functions handling $_FILES or wp_upload_bits within the plugin files.
    Affected if File upload functionality is present in the plugin and accessible to Subscriber role users

You are affected if Restaurant Zone version 0.7.8 or lower is installed AND subscriber-level users can access the file upload functionality.

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

Update Restaurant Zone to the latest patched version immediately. If no patch is available, disable subscriber registration or remove the plugin until a fix is released.

Recommended fix Moderate confidence

Latest stable version of Restaurant Zone (vendor should publish the specific fixed release)

  1. 1. First, confirm the exact version of Restaurant Zone currently installed on your WordPress site.
  2. 2. Check the official WordPress plugin repository or the developer's website for the latest version of Restaurant Zone.
  3. 3. Before upgrading, perform a complete backup of your WordPress site including database and files.
  4. 4. Test the upgrade in a staging environment if possible to ensure compatibility with your theme and other plugins.
  5. 5. If a fixed version is available from the vendor, upgrade to that version to resolve the arbitrary file upload vulnerability.
  6. 6. After upgrading, verify that subscribers can no longer upload files with dangerous extensions (e.g., .php, .exe, .js).
  7. 7. Review uploaded files on your server to ensure no malicious files were uploaded exploiting this vulnerability.
Caveat Review plugin/theme compatibility notes before upgrading, as minor version jumps may include template or functionality changes

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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