dbcve.org
EasyrecipeWordPress extension · Easyrecipe Project

CVE-2023-46779

HIGH · 8.8 CVSS v3.1 Published 2023-11-06
Fix available
A fix is available. Upgrade to after 3.5.3251 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in EasyRecipe plugin <= 3.5.3251 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

Cross-Site Request Forgery (CSRF) vulnerability in the EasyRecipe WordPress plugin affecting versions 3.5.3251 and prior. The vulnerability allows attackers to trick authenticated users into performing unintended actions by forging malicious requests, potentially leading to unauthorized configuration changes or data manipulation within the recipe management functionality.

MitigationUpdate EasyRecipe plugin to the latest version which should contain anti-CSRF token implementation. Alternatively, implement anti-CSRF tokens (nonces) on all state-changing actions within the plugin and verify WordPress nonce verification is properly enforced on form submissions and AJAX requests.

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
EasyrecipeWordPress extension
Affected:<= 3.5.3251

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Identify if EasyRecipe plugin is installed
    Access your WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'EasyRecipe' or 'Easyrecipe' in the plugin list. Alternatively, check if the /wp-content/plugins/easyrecipe/ directory exists on your server.
    Affected if The EasyRecipe plugin is found in the WordPress installation.
  2. Check the installed EasyRecipe version
    In WordPress admin, go to Plugins > Installed Plugins and locate EasyRecipe. The version number is displayed below the plugin name. Alternatively, open the main plugin file (usually easyrecipe.php) and look for the 'Version' header in the plugin comment block.
    Affected if The installed version is 3.5.3251 or any earlier version.
  3. Inspect recipe management forms for nonce fields
    Navigate to any EasyRecipe form (such as adding or editing a recipe in the WordPress admin). View the page source (right-click > View Page Source) and search for input fields with names containing 'nonce', '_wpnonce', or 'security'. Check if these nonce fields are present within forms that modify recipe data.
    Affected if State-changing forms (create, edit, delete recipes) lack nonce token input fields.
  4. Verify AJAX requests include nonce verification
    Use browser developer tools (Network tab) to intercept an AJAX request made by EasyRecipe when saving or modifying a recipe. Check the request parameters for a nonce value (commonly passed as 'nonce', '_wpnonce', or '_ajax_nonce' parameters).
    Affected if AJAX requests that modify data do not include nonce parameters.
  5. Confirm WordPress nonce verification is enforced in code
    If you have code access, review EasyRecipe PHP files that handle form submissions and AJAX callbacks. Look for calls to WordPress functions such as 'wp_verify_nonce', 'check_admin_referer', 'check_ajax_referer', or 'wp_nonce_field' before processing state-changing operations.
    Affected if Form handlers and AJAX callbacks lack WordPress nonce verification calls.

You are affected if EasyRecipe plugin version 3.5.3251 or earlier is installed AND the plugin forms/AJAX handlers do not implement WordPress nonce tokens for CSRF protection.

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 a release after 3.5.3251
Interim mitigation

Update EasyRecipe plugin to the latest version which should contain anti-CSRF token implementation. Alternatively, implement anti-CSRF tokens (nonces) on all state-changing actions within the plugin and verify WordPress nonce verification is properly enforced on form submissions and AJAX requests.

Recommended fix Moderate confidence

Update to the latest available version of EasyRecipe (the vendor has released a fix in a version higher than 3.5.3251)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate EasyRecipe in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version that addresses the CSRF vulnerability
  5. 5. Alternatively, download the latest version from the official WordPress plugin repository and upload it manually
  6. 6. After updating, verify the plugin is functioning correctly and test that CSRF protections are in place

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

Fix this in Easyrecipe Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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