dbcve.org
Element PackWordPress extension · Bdthemes

CVE-2024-39667

MEDIUM · 5.4 CVSS v3.1 Published 2024-08-01
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
Improper Neutralization of Input During Web Page Generation (XSS or '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.11.

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 XSS vulnerability in BdThemes Element Pack Elementor Addons allows attackers to inject malicious JavaScript through unsanitized input fields. The malicious payload is stored in the database and executes when other users view affected pages in the Elementor builder.

MitigationUpdate to a version beyond 5.6.11 when available, or apply WordPress-appropriate input sanitization and output escaping at the vulnerable input points within the plugin.

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 version installed
    Check the installed version via WordPress admin: navigate to Plugins > Installed Plugins > look for 'Element Pack' and read the version number. Alternatively, check the plugin header in wp-content/plugins/element-pack/modules.php or similar main plugin file.
    Affected if The displayed version is lower than 5.6.12 (e.g., 5.6.11, 5.6.10, etc.)
  2. Confirm Elementor builder is in use
    Check if the Elementor page builder plugin is active and if Element Pack widgets are being used on any pages/posts. Inspect the post meta in wp_postmeta table for _elementor_data containing 'element_pack' references.
    Affected if Element Pack widgets are actively used on the site and the plugin version is below 5.6.12
  3. Inspect database for suspicious stored scripts
    Query the wp_postmeta table for stored XSS patterns. Run: SELECT * FROM wp_postmeta WHERE meta_value LIKE '%<script%' OR meta_value LIKE '%onerror=%' OR meta_value LIKE '%javascript:%' - review any results that involve Element Pack widget settings.
    Affected if Malicious JavaScript payloads are found stored in postmeta related to Element Pack widget configurations
  4. Review recent admin-entered content
    Examine recently created or modified Elementor pages that use Element Pack widgets. Focus on text input fields in widget settings (e.g., advanced text, heading, button widgets) for unsanitized HTML/JavaScript.
    Affected if Unsanitized script tags or event handlers are present in widget input fields in the database

A user is affected if BdThemes Element Pack version is below 5.6.12 AND Element Pack widgets with unsanitized user input are stored 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 5.6.12 or later
Fixed in 5.6.12
Interim mitigation

Update to a version beyond 5.6.11 when available, or apply WordPress-appropriate input sanitization and output escaping at the vulnerable input points within the plugin.

Recommended fix High confidence

5.6.12

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Element Pack Elementor Addons' in the plugin list
  4. Check if the currently installed version is below 5.6.12
  5. If vulnerable, click 'Update Now' to update Element Pack to version 5.6.12 or later
  6. Alternatively, go to Dashboard > Updates and update Element Pack from there
  7. After update, verify the new version number reflects 5.6.12 or higher

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

Fix this in Element Pack Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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