dbcve.org
Beaver Builder AddonsWordPress extension · Wpzoom

CVE-2024-30424

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-19
Fix available
A fix is available. Upgrade to 1.3.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 ('Cross-site Scripting') vulnerability in WPZOOM Beaver Builder Addons by WPZOOM wpzoom-addons-for-beaver-builder allows Stored XSS.This issue affects Beaver Builder Addons by WPZOOM: from n/a through <= 1.3.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 · high confidence

Stored Cross-site Scripting (XSS) vulnerability in WPZOOM Beaver Builder Addons plugin allows attackers to inject malicious JavaScript through unsanitized user input that gets stored in the database and executed when other users view affected pages.

MitigationUpdate to the latest version of WPZOOM Beaver Builder Addons which should include proper input sanitization and output encoding; alternatively, apply output escaping functions (esc_html, esc_attr, wp_kses) to all user-supplied data before rendering.

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
Beaver Builder AddonsWordPress extension
Affected:< 1.3.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. Check installed plugin version
    Go to WordPress admin > Plugins > WPZOOM Beaver Builder Addons and note the version number displayed, or check the plugin header in /wp-content/plugins/wpzoom-beaver-builder-addons/
    Affected if Version is lower than 1.3.5 (e.g., 1.3.4, 1.3.3, etc.)
  2. Verify plugin is active
    Confirm the WPZOOM Beaver Builder Addons plugin is enabled in the WordPress plugins list
    Affected if Plugin is active and vulnerable version is installed
  3. Identify user input modules
    In Beaver Builder editor, locate WPZOOM custom modules that accept user input (such as heading, text, button, or custom content modules from this plugin)
    Affected if Any WPZOOM module that allows text input is being used on a page
  4. Inspect stored data for unsanitized input
    Check the database tables (typically wp_posts or wp_postmeta) for content created with WPZOOM modules - look for raw HTML or script tags in the content fields
    Affected if Raw HTML/script tags appear stored in the database without encoding
  5. Review source code for output escaping
    Examine the plugin PHP files in /wp-content/plugins/wpzoom-beaver-builder-addons/ for missing esc_html, esc_attr, or wp_kses functions around user-supplied data when output to page
    Affected if Output functions do not include proper escaping for user input fields

You are affected if the WPZOOM Beaver Builder Addons plugin version is below 1.3.5 AND the plugin is active with WPZOOM modules accepting user input on your site.

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

Update to the latest version of WPZOOM Beaver Builder Addons which should include proper input sanitization and output encoding; alternatively, apply output escaping functions (esc_html, esc_attr, wp_kses) to all user-supplied data before rendering.

Recommended fix High confidence

1.3.5

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'WPZOOM Beaver Builder Addons' (or 'Beaver Builder Addons by WPZOOM') in the plugin list
  4. Click 'Update Now' if an update is available, or deactivate and reinstall the plugin
  5. Verify the updated version is 1.3.5 or higher

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

Fix this in Beaver Builder Addons Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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