dbcve.org
Blossom SpaWordPress extension · Blossomthemes

CVE-2024-2107

HIGH · 7.5 CVSS v3.1 Published 2024-03-12
Fix available
A fix is available. Upgrade to 1.3.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
The Blossom Spa theme for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.3.3 via generated source. This makes it possible for unauthenticated attackers to extract sensitive data including contents of password-protected or scheduled posts.

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 Blossom Spa WordPress theme (versions up to 1.3.3) improperly exposes sensitive content through its generated source code output. Unauthenticated attackers can retrieve the full content of password-protected posts and scheduled (future-published) posts that should only be visible to authorized users or after publication.

MitigationUpdate to the latest version of the Blossom Spa theme if a patched version is available; otherwise consider switching to an actively maintained theme or hiring a developer to patch the access control logic in the theme's template files.

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 SpaWordPress extension
Affected:< 1.3.4

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Confirm Blossom Spa theme is installed
    In WordPress admin, go to Appearance > Themes and verify that the Blossom Spa theme by Blossomthemes is currently active
    Affected if The Blossom Spa theme is active on the WordPress site
  2. Identify the installed theme version
    Access the theme's style.css file via FTP or file manager (typically in wp-content/themes/blossom-spa/) and locate the 'Version' header in the file comments, or check via WordPress theme details panel
    Affected if The version number is lower than 1.3.4 (e.g., 1.3.3, 1.3.2, etc.)
  3. Test for exposure of password-protected posts
    Using a browser in private/incognito mode (unauthenticated), attempt to access a password-protected post by navigating directly to its URL and bypassing the password prompt, or inspect the page source to see if protected content is rendered in the HTML
    Affected if The full content of password-protected posts is visible without entering the password, or content appears in the page source
  4. Test for exposure of scheduled posts
    Create a test scheduled post set to future publication, then attempt to access it via direct URL while logged out (unauthenticated) or inspect the page source of any existing scheduled posts
    Affected if Scheduled (future-published) posts are accessible to unauthenticated users or their content appears in generated source code

You are affected if the Blossom Spa theme version is below 1.3.4 AND password-protected or scheduled posts are visible to unauthenticated users.

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.3.4 or later
Fixed in 1.3.4
Interim mitigation

Update to the latest version of the Blossom Spa theme if a patched version is available; otherwise consider switching to an actively maintained theme or hiring a developer to patch the access control logic in the theme's template files.

Recommended fix High confidence

Blossom Spa theme version 1.3.4

  1. 1. Update the Blossom Spa theme to version 1.3.4 or later via WordPress admin dashboard under Appearance > Themes, or
  2. 2. If using a child theme, ensure the parent theme is updated to 1.3.4
  3. 3. Verify the update completed successfully
  4. 4. Test that password-protected and scheduled posts are no longer accessible to unauthenticated users

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

Fix this in Blossom Spa Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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