dbcve.org
Element PackWordPress extension · Bdthemes

CVE-2024-3925

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-12
Fix available
A fix is available. Upgrade to 5.6.12 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
The Element Pack Elementor Addons (Header Footer, Template Library, Dynamic Grid & Carousel, Remote Arrows) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Creative Button widget in all versions up to, and including, 5.6.11 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 Element Pack Elementor Addons plugin for WordPress contains a stored XSS vulnerability in its Creative Button widget. Authenticated attackers with contributor-level access can inject arbitrary JavaScript through unsanitized user-supplied attributes. The plugin fails to properly sanitize input and escape output, allowing malicious scripts to persist and execute whenever users access affected pages.

MitigationUpdate the Element Pack plugin to version 5.6.12 or later, which includes proper input sanitization and output escaping for the Creative Button widget attributes. If immediate update is not possible, restrict contributor-level access to widget editing.

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.12

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 Element Pack plugin installation and version
    Go to WordPress Admin > Plugins and locate 'Element Pack Elementor Addons' by Bdthemes. Check the version number displayed. Alternatively, check the plugin file header at /wp-content/plugins/bdt-element-pack/bdt-element-pack.php for the 'Version' define.
    Affected if The installed version is below 5.6.12
  2. Confirm Creative Button widget is in use
    Search your site for pages, posts, or templates that contain the Creative Button widget. In Elementor editor, look for the 'Creative Button' widget in the Element Pack widget list. Check your site's published pages for any instances of this specific widget.
    Affected if The Creative Button widget from Element Pack is present on any live page or template
  3. Verify contributor-level user access to Elementor
    Go to WordPress Admin > Users > Roles. Check if any user role with 'Contributor' level or similar limited permissions has the capability to access and edit using Elementor Page Builder. This is typically indicated by the 'edit_elementor' or 'access_elementor' capability assigned to contributor roles.
    Affected if Contributor-level users or any user role below Administrator/Editor has permission to use the Elementor editor and edit widgets

Your environment is affected if the installed Element Pack version is below 5.6.12, the Creative Button widget is actively used on your site, and contributor-level users have access to Elementor widget editing capabilities.

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.12 or later
Fixed in 5.6.12
Interim mitigation

Update the Element Pack plugin to version 5.6.12 or later, which includes proper input sanitization and output escaping for the Creative Button widget attributes. If immediate update is not possible, restrict contributor-level access to widget editing.

Recommended fix High confidence

Element Pack version 5.6.12 or higher

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Element Pack plugin
  4. 4. Check if current version is below 5.6.12
  5. 5. If vulnerable, click 'Update Now' to upgrade to version 5.6.12 or higher
  6. 6. Verify the update completed successfully
  7. 7. Test the Creative Button widget to confirm the XSS vulnerability is remediated

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-3925 — 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-3925 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