dbcve.org
BlockboosterWordPress extension · Cozythemes

CVE-2024-43979

CRITICAL · 9.8 CVSS v3.1 Published 2024-11-01
Fix available
A fix is available. Upgrade to 1.0.11 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Missing Authorization vulnerability in CozyThemes Blockbooster allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Blockbooster: from n/a through 1.0.10.

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

Missing authorization vulnerability in CozyThemes Blockbooster WordPress plugin allows unauthenticated attackers to access administrative or privileged functionality that should be protected by access control lists. The plugin fails to properly validate user permissions before executing certain actions, enabling remote attackers to bypass authentication and perform privileged operations.

MitigationUpdate to the latest patched version of Blockbooster when available. If no patch exists, temporarily disable the plugin or implement web application firewall rules to restrict access to the vulnerable endpoints until a fix is released.

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
BlockboosterWordPress extension
Affected:< 1.0.11

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Verify Blockbooster plugin is installed
    Check the WordPress plugins directory for the Blockbooster folder: navigate to /wp-content/plugins/ or use WP-CLI: wp plugin list --name=blockbooster
    Affected if The Blockbooster plugin folder exists in the WordPress installation
  2. Identify installed Blockbooster version
    Check the main plugin file (blockbooster.php) for the Version header, or use WP-CLI: wp plugin get blockbooster --field=version
    Affected if The installed version is lower than 1.0.11
  3. Verify WordPress user authentication is required for plugin actions
    Test accessing common WordPress admin actions via the plugin (such as plugin settings pages or AJAX endpoints) while logged out as a guest user
    Affected if Unauthenticated requests to Blockbooster-related endpoints return successful responses instead of requiring login
  4. Inspect plugin capability checks
    Review the main plugin PHP file for function calls like current_user_can(), wp_verify_nonce(), or check_admin_referer() before executing privileged operations
    Affected if No capability or nonce verification is performed before sensitive plugin functions execute

You are affected if the Blockbooster plugin is installed and its version is below 1.0.11, and unauthenticated users can access privileged functionality that should require authorization.

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.0.11 or later
Fixed in 1.0.11
Interim mitigation

Update to the latest patched version of Blockbooster when available. If no patch exists, temporarily disable the plugin or implement web application firewall rules to restrict access to the vulnerable endpoints until a fix is released.

Recommended fix High confidence

1.0.11

  1. Backup your WordPress site and database before performing any updates
  2. Update the Blockbooster plugin to version 1.0.11 through the WordPress admin dashboard (Plugins > Installed Plugins > Update Now) or via wp-cli: wp plugin update blockbooster
  3. Verify the update was successful by confirming the installed version is 1.0.11
  4. Test that the Blockbooster functionality continues to work as expected after the update

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

Fix this in Blockbooster 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-2024-43979 — 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-43979 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