dbcve.org
Woocommerce FoodWordPress extension · Exthemes

CVE-2024-13792

CRITICAL · 9.8 CVSS v3.1 Published 2025-02-20
Fix available
A fix is available. Upgrade to 3.3.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
The WooCommerce Food - Restaurant Menu & Food ordering plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 3.3.2. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes.

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 confidence

The WooCommerce Food plugin for WordPress contains a shortcode injection vulnerability in versions up to 3.3.2. The plugin passes unsanitized user input directly to WordPress's do_shortcode() function, allowing unauthenticated attackers to execute arbitrary shortcodes. This can lead to data theft, privilege escalation, or remote code execution depending on other installed plugins' exposed shortcodes.

MitigationUpdate to a patched version of the plugin once released by the vendor. Until then, consider disabling the plugin or deploying a WAF rule to block requests targeting the vulnerable endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Woocommerce FoodWordPress extension
Affected:< 3.3.3

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

CVSS:3.1/AV:N/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm the plugin is installed
    Navigate to WordPress Admin > Plugins or use WP-CLI: wp plugin list --search='woocommerce-food' to list the plugin
    Affected if The plugin 'woocommerce-food' or 'Exthemes Woocommerce Food' appears in the installed plugins list
  2. Check the installed version
    In WordPress Admin > Plugins, click on the WooCommerce Food plugin to view its version, or read the plugin header from the main PHP file in wp-content/plugins/woocommerce-food/ (or similar path), or run: wp plugin get woocommerce-food --field=version
    Affected if The version number is lower than 3.3.3 (e.g., 3.3.2, 3.3.1, 3.3.0, etc.)
  3. Identify if shortcode processing is accessible
    Check if the plugin exposes any frontend endpoints or AJAX actions that accept user input and process it through do_shortcode(). Review the plugin PHP files for calls to do_shortcode() with $_REQUEST, $_POST, or $_GET variables, or test common parameter names used by the plugin.
    Affected if The plugin processes user-supplied input through do_shortcode() without sanitization and the vulnerable endpoint is accessible to unauthenticated users
  4. Check for exploitable shortcodes on the site
    In WordPress Admin > Shortcodes, or use WP-CLI: wp shortcode list, to enumerate available shortcodes. Review what shortcodes are registered by other active plugins (e.g., contact forms, content embedding, user management) that could be leveraged if shortcode execution is achieved.
    Affected if Shortcodes that can read sensitive data, create users, or modify content are registered and active on the site

Your environment is affected if the WooCommerce Food plugin is installed with a version lower than 3.3.3 and the vulnerable shortcode processing functionality is accessible to unauthenticated users.

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
Upgrade available Upgrade to 3.3.3 or later
Fixed in 3.3.3
Interim mitigation

Update to a patched version of the plugin once released by the vendor. Until then, consider disabling the plugin or deploying a WAF rule to block requests targeting the vulnerable endpoint.

Recommended fix High confidence

3.3.3

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find the 'WooCommerce Food' plugin
  5. 5. Check if an update to version 3.3.3 is available
  6. 6. If an update is available, click 'Update Now' to update to version 3.3.3
  7. 7. If no update is shown in the plugin repository, download version 3.3.3 from the vendor (CodeCanyon) and upload it manually via Plugins > Add New > Upload Plugin
  8. 8. Verify the update was successful by checking the plugin version displayed in the plugins list

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

Fix this in Woocommerce Food Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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