dbcve.org
Blossom Recipe MakerWordPress extension · Blossomthemes

CVE-2022-37338

MEDIUM · 5.4 CVSS v3.1 Published 2022-09-23
Fix available
A fix is available. Upgrade to after 1.0.7 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
Multiple Authenticated (contributor+) Stored Cross-Site Scripting (XSS) vulnerabilities in Blossom Recipe Maker plugin <= 1.0.7 at WordPress.

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

Multiple stored XSS vulnerabilities exist in the Blossom Recipe Maker WordPress plugin (versions <= 1.0.7) where authenticated users with contributor-level permissions or higher can inject malicious JavaScript code through plugin input fields. The injected scripts are stored in the database and execute when other users view the affected content, potentially compromising administrator sessions or stealing sensitive data.

MitigationUpdate the Blossom Recipe Maker plugin to a version newer than 1.0.7, which should include proper input sanitization and output escaping for all user-supplied data.

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
Blossom Recipe MakerWordPress extension
Affected:<= 1.0.7

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 Blossom Recipe Maker plugin is installed
    Navigate to WordPress admin dashboard > Plugins, locate 'Blossom Recipe Maker' (or 'Blossomthemes Blossom Recipe Maker'), and note the installed version number displayed in the plugins list.
    Affected if The plugin is installed and the version listed is 1.0.7 or lower.
  2. Check plugin version in plugin files
    Access the plugin directory via FTP or file manager at wp-content/plugins/blossom-recipe-maker/ and open the main plugin PHP file (such as index.php orblossom-recipe-maker.php). Look for the 'Version' header in the plugin file comments to confirm the exact version.
    Affected if The version number in the plugin file header is 1.0.7 or lower.
  3. Identify contributor-level or higher users
    In WordPress admin, go to Users > All Users and review the 'Role' column. Note any users assigned the roles of Contributor, Author, Editor, or Administrator.
    Affected if There are users with Contributor, Author, Editor, or Administrator roles who have access to create or edit recipe content.
  4. Inspect database for stored XSS in recipe content
    Access the WordPress database via phpMyAdmin or command line. Query the wp_posts table for recipe-related posts: SELECT * FROM wp_posts WHERE post_type LIKE '%recipe%' OR post_content LIKE '%blossom-recipe%'. Examine the post_content and any custom meta fields for suspicious script tags, javascript:, or event handler attributes (onclick, onerror, onload).
    Affected if Any records in wp_posts (or related meta tables) contain raw script tags, javascript: URIs, or HTML event handlers within recipe content fields.
  5. Review recipe settings for unescaped output
    Navigate to Recipes in the admin sidebar, open any existing recipe, and inspect fields such as recipe title, description, ingredients list, and instructions. View the page frontend and view page source to check if user-entered text renders with unescaped HTML characters.
    Affected if User-supplied text in recipe fields displays raw HTML tags or executes JavaScript when viewed on the frontend.

A user is affected if the Blossom Recipe Maker plugin is installed at version 1.0.7 or lower AND any contributor-level or higher user account exists that could have injected malicious scripts into recipe content fields.

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

Update the Blossom Recipe Maker plugin to a version newer than 1.0.7, which should include proper input sanitization and output escaping for all user-supplied data.

Recommended fix Moderate confidence

Latest version of Blossom Recipe Maker (version higher than 1.0.7)

  1. 1. Log in to the WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate Blossom Recipe Maker in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is running on a version newer than 1.0.7
  6. 6. Test the recipe submission functionality to ensure the plugin still works correctly
  7. 7. Clear any caching plugins if present, then verify the site loads correctly

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

Fix this in Blossom Recipe Maker Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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