dbcve.org
Element PackWordPress extension · Bdthemes

CVE-2024-32572

MEDIUM · 5.4 CVSS v3.1 Published 2024-04-18
Fix available
A fix is available. Upgrade to 5.6.1 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 BdThemes Element Pack Elementor Addons allows Stored XSS.This issue affects Element Pack Elementor Addons: from n/a through 5.6.0.

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

Stored Cross-Site Scripting (XSS) vulnerability in BdThemes Element Pack Elementor Addons allows attackers to inject malicious JavaScript payloads through unsanitized input fields. The injected script executes in the browsers of users who view affected pages, potentially leading to session hijacking, credential theft, or defacement.

MitigationUpdate to the latest version of Element Pack Elementor Addons when available. If no patch exists, implement proper input sanitization using WordPress sanitization functions and output escaping (esc_html, esc_attr) on 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
Element PackWordPress extension
Affected:< 5.6.1

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. Confirm Element Pack plugin is installed
    Navigate to WordPress admin > Plugins and locate 'Element Pack Elementor Addons' by BdThemes, or check the plugins directory for /wp-content/plugins/bdthemes-element-pack/
    Affected if The plugin is installed and active in WordPress
  2. Identify installed version number
    In WordPress admin > Plugins, click on the plugin name to view details, or inspect the main plugin file (e.g., /wp-content/plugins/bdthemes-element-pack/bdthemes-element-pack.php) and look for the Version: X.X.X declaration
    Affected if The installed version is lower than 5.6.1 (e.g., 5.6.0, 5.5.0, etc.)
  3. Review Elementor pages and posts for Element Pack widgets
    Check pages/posts built with Elementor that use Element Pack widgets. Navigate to WP admin > Pages or Posts, edit a page with Elementor, and look for Element Pack widgets in the left panel
    Affected if Pages or posts contain Element Pack widgets with user-input fields (text inputs, textareas, form fields, or custom content fields)
  4. Inspect database for suspicious script injections
    Check WordPress postmeta and options tables for script tags, javascript: URIs, or event handlers (onerror, onload, onmouseover) in any content associated with Element Pack widgets
    Affected if Database contains stored scripts in fields associated with Element Pack widget inputs that were not properly escaped

A user is affected if BdThemes Element Pack is installed with a version lower than 5.6.1 and contains pages using Element Pack widgets with unsanitized input fields that could store malicious scripts.

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

Update to the latest version of Element Pack Elementor Addons when available. If no patch exists, implement proper input sanitization using WordPress sanitization functions and output escaping (esc_html, esc_attr) on all user-supplied data before rendering.

Recommended fix High confidence

5.6.1

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Element Pack - Elementor Addons' plugin
  4. Check the current version to confirm it is below 5.6.1
  5. Click 'Update now' when an update to version 5.6.1 or later is available
  6. After updating, clear any caching plugins you use
  7. Verify the update was successful by checking the plugin version
Caveat Review the plugin changelog for any changes that may affect your site functionality before updating

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

Fix this in Element Pack 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-32572 — 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-32572 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