dbcve.org
Cards For Beaver BuilderWordPress extension · Brainstormforce

CVE-2024-37278

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-22
Fix available
A fix is available. Upgrade to 1.1.5 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
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Pratik Chaskar Cards for Beaver Builder.This issue affects Cards for Beaver Builder: from n/a through 1.1.4.

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

This is a stored Cross-Site Scripting (XSS) vulnerability in the Cards for Beaver Builder WordPress plugin. The plugin fails to properly sanitize user input or encode output when generating web pages, allowing malicious scripts to be injected and executed in the context of other users' browsers.

MitigationUpgrade to version 1.1.5 or later which should contain proper input sanitization and output encoding. If no update is available, disable the plugin until a patched version 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
Cards For Beaver BuilderWordPress extension
Affected:< 1.1.5

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 plugin installation
    Locate the plugin folder in wp-content/plugins/ (typically named 'bb-plugin-cards' or similar) or check via WordPress admin under Plugins > Installed Plugins
    Affected if The plugin folder 'Cards for Beaver Builder' or 'bb-plugin-cards' exists in the plugins directory
  2. Check installed version
    View the plugin's main PHP file header (usually in the plugin folder root) for the 'Version' comment, or check the WordPress plugin admin page listing
    Affected if The version number is less than 1.1.5 (e.g., 1.1.4, 1.1.3, etc.)
  3. Confirm plugin is active
    Check WordPress admin under Plugins > Installed Plugins to see if the Cards for Beaver Builder plugin is activated
    Affected if The plugin shows as 'Active' in the WordPress plugin list
  4. Inspect saved card content
    Query the WordPress database tables (typically wp_posts or wp_postmeta) for any post content or meta entries containing the plugin's custom post type or card module data
    Affected if Any card content stored in the database contains unsanitized HTML script tags or JavaScript event handlers (e.g., <script>, onerror=, onload=, javascript:)

You are affected if the Cards for Beaver Builder plugin is installed, active, and running a version earlier than 1.1.5 with user-created card content present in the database.

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.5 or later
Fixed in 1.1.5
Interim mitigation

Upgrade to version 1.1.5 or later which should contain proper input sanitization and output encoding. If no update is available, disable the plugin until a patched version is released.

Recommended fix High confidence

1.1.5

  1. Update the Cards for Beaver Builder plugin to version 1.1.5 or later via the WordPress admin dashboard (Plugins > Update Now), or via command line using `wp plugin update cards-for-beaver-builder`
  2. After updating, verify the plugin version shows 1.1.5 or higher in the installed plugins list
  3. Consider clearing any caching mechanisms (page caches, CDN caches) if the plugin is used on the frontend

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

Fix this in Cards For Beaver Builder Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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