dbcve.org
Wp Recipe MakerWordPress extension · Bootstrapped

CVE-2024-0384

MEDIUM · 5.4 CVSS v3.1 Published 2024-02-05
Fix available
A fix is available. Upgrade to after 9.1.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 WP Recipe Maker plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Recipe Notes in all versions up to, and including, 9.1.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 WP Recipe Maker plugin for WordPress versions up to 9.1.0 contains a stored XSS vulnerability in the Recipe Notes feature. Authenticated users with contributor-level or higher permissions can inject arbitrary JavaScript through unsanitized input that is not properly escaped on output, causing the script to execute whenever the recipe page is accessed.

MitigationUpdate the WP Recipe Maker plugin to version 9.1.1 or later. If immediate updating is not possible, implement input sanitization (sanitize_text_field) and output escaping (esc_html/esc_attr) on the Recipe Notes field in the plugin code.

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
Wp Recipe MakerWordPress extension
Affected:<= 9.1.0

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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. Verify WP Recipe Maker plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Recipe Maker' in the list. Note the version number displayed below the plugin name.
    Affected if The plugin is installed and the version is 9.1.0 or lower
  2. Confirm the installed version is within affected range
    Compare the installed version number to the affected range. The vulnerability affects versions up to and including 9.1.0.
    Affected if The installed version is 9.1.0 or any version lower than 9.1.0
  3. Identify if Recipe Notes feature is in use
    Query the WordPress database for recipes that have content in the notes field. This can be done via WP admin by viewing individual recipes, or by checking the postmeta table for postmeta_key containing 'notes' with non-empty meta_value.
    Affected if There are recipes with populated Recipe Notes fields on the site
  4. Check for contributor-level or higher user accounts
    In WordPress admin, go to Users > All Users and review the roles assigned. Contributor, Author, Editor, and Administrator roles all have permissions that meet or exceed the contributor-level requirement for this vulnerability.
    Affected if Any user account with contributor, author, editor, or administrator role exists on the site

If WP Recipe Maker version 9.1.0 or lower is installed, the Recipe Notes feature contains data, and contributor-level or higher users exist, the environment is affected by this stored XSS vulnerability.

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 9.1.0
Interim mitigation

Update the WP Recipe Maker plugin to version 9.1.1 or later. If immediate updating is not possible, implement input sanitization (sanitize_text_field) and output escaping (esc_html/esc_attr) on the Recipe Notes field in the plugin code.

Recommended fix High confidence

WP Recipe Maker 9.2.0 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate WP Recipe Maker in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/wp-recipe-maker/ and upload it manually via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is running version 9.2.0 or higher

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

Fix this in Wp Recipe Maker Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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