dbcve.org
Recipe Card Blocks For Gutenberg \& ElementorWordPress extension · Wpzoom

CVE-2024-43293

HIGH · 8.8 CVSS v3.1 Published 2024-11-01
Fix available
A fix is available. Upgrade to 3.3.2 or later.
See remediation →
94/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
Missing Authorization vulnerability in WPZOOM Recipe Card Blocks for Gutenberg & Elementor allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Recipe Card Blocks for Gutenberg & Elementor: from n/a through 3.3.1.

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

Missing authorization vulnerability in WPZOOM Recipe Card Blocks for Gutenberg & Elementor plugin allows attackers to exploit incorrectly configured access control security levels. The vulnerability enables unauthorized access to certain functionality that should be restricted, likely through AJAX endpoints or frontend submission handlers lacking proper capability checks or nonce validation.

MitigationUpdate to version 3.3.2 or later which contains the authorization fix; alternatively, audit and add proper authorization checks (current_user_can, nonce verification) to all sensitive plugin actions.

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
Recipe Card Blocks For Gutenberg \& ElementorWordPress extension
Affected:< 3.3.2

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Check if WPZOOM Recipe Card Blocks plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WPZOOM Recipe Card Blocks for Gutenberg & Elementor' in the list
    Affected if The plugin appears in the installed plugins list and is activated
  2. Identify the installed plugin version
    Click 'View details' on the plugin in the WordPress plugins page, or check the plugin header in /wp-content/plugins/recipe-card-blocks/ folder for the 'Version' field
    Affected if The version number displayed is lower than 3.3.2 (for example: 3.3.1, 3.3.0, 3.2.5, etc.)
  3. Verify AJAX endpoints lack authorization checks
    Inspect plugin PHP files in /wp-content/plugins/recipe-card-blocks/ for AJAX action handlers (add_action calls with 'wp_ajax_' or 'wp_ajax_nopriv_') and check if they contain current_user_can() calls or nonce verification before executing sensitive operations
    Affected if AJAX handlers exist without proper current_user_can() capability checks or nonce validation logic
  4. Test frontend submission handlers for authorization
    Review frontend submission code in plugin files (especially functions handling recipe submissions or user input) to see if they verify user capabilities before allowing data modifications
    Affected if Frontend handlers process requests without verifying the current user has appropriate permissions

Your environment is affected if the WPZOOM Recipe Card Blocks plugin is installed with a version lower than 3.3.2 and contains AJAX or submission handlers that lack proper authorization checks.

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.2 or later
Fixed in 3.3.2
Interim mitigation

Update to version 3.3.2 or later which contains the authorization fix; alternatively, audit and add proper authorization checks (current_user_can, nonce verification) to all sensitive plugin actions.

Recommended fix High confidence

3.3.2

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Recipe Card Blocks for Gutenberg & Elementor' (WPZOOM Recipe Card)
  4. If an update is available, click 'Update Now' to upgrade to version 3.3.2
  5. Alternatively, go to Dashboard > Updates and select the plugin to update
  6. After updating, verify the plugin version is 3.3.2 in the Plugins list

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

Fix this in Recipe Card Blocks For Gutenberg \& Elementor 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-43293 — 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-43293 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