dbcve.org
Blossom ShopWordPress extension · Blossomthemes

CVE-2024-37412

HIGH · 8.8 CVSS v3.1 Published 2025-01-02
Fix available
A fix is available. Upgrade to 1.1.8 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 blossomthemes Blossom Shop blossom-shop allows Cross Site Request Forgery.This issue affects Blossom Shop: from n/a through <= 1.1.7.

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 Blossom Shop WordPress theme (versions through 1.1.7) allows attackers to induce authenticated users to perform unintended actions by tricking them into visiting malicious pages or clicking crafted links.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing operations, validate request referrers, and add SameSite cookie attributes to session cookies.

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 ShopWordPress extension
Affected:< 1.1.8

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. Check installed Blossom Shop theme version
    In WordPress admin, go to Appearance > Themes to see the installed version of Blossom Shop theme. Alternatively, check the style.css file in wp-content/themes/blossom-shop/ for the 'Version:' comment header.
    Affected if The installed version is 1.1.7 or lower (anything below 1.1.8)
  2. Identify theme directory path
    Navigate to wp-content/themes/ in your WordPress installation and confirm the theme folder is named 'blossom-shop' or similar variant of Blossom Shop.
    Affected if The Blossom Shop theme directory exists on the server
  3. Inspect PHP files for nonce verification
    Search theme PHP files (especially in includes/ or any file handling form submissions/AJAX) for 'wp_nonce_field', 'wp_nonce_url', or 'check_admin_referer' functions. Use grep or manually open files to search for these nonce verification calls.
    Affected if No nonce verification functions are found in files handling state-changing operations
  4. Check AJAX handlers for CSRF protection
    Search for 'add_action' calls with 'wp_ajax' hooks and verify if they include nonce validation using 'check_ajax_referer' or 'wp_verify_nonce' before processing requests.
    Affected if AJAX handlers lack nonce validation checks

You are affected if the installed Blossom Shop theme version is below 1.1.8 AND sensitive operations (forms, AJAX requests) lack proper nonce verification code.

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 1.1.8 or later
Fixed in 1.1.8
Interim mitigation

Implement anti-CSRF tokens (nonces) on all state-changing operations, validate request referrers, and add SameSite cookie attributes to session cookies.

Recommended fix Moderate confidence

Blossom Shop version 1.1.8

  1. 1. Back up your WordPress site and database before performing any updates.
  2. 2. Navigate to the WordPress admin dashboard for your site.
  3. 3. Go to Dashboard > Updates or Plugins > Installed Plugins.
  4. 4. Update the Blossom Shop theme to version 1.1.8 or later.
  5. 5. Verify the update was successful by checking the theme version in Appearance > Themes.
  6. 6. Test critical functionality on the site to ensure the update did not break any features.

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

Fix this in Blossom Shop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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