dbcve.org
Element PackWordPress extension · Bdthemes

CVE-2024-30185

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-27
Fix available
A fix is available. Upgrade to 5.5.4 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.5.3.

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 authenticated or unauthenticated attackers to inject malicious JavaScript code through unsanitized input fields within the Elementor addon components. The malicious payload is persistently stored and executes when other users view the compromised pages in the Elementor page builder.

MitigationUpdate Element Pack Elementor Addons to the latest patched version once available. As a temporary measure, disable or remove the plugin until a fix is released. Review and sanitize all user-supplied input fields 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.5.4

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 > Installed Plugins and look for 'Element Pack' or 'BdThemes Element Pack' in the list of active plugins
    Affected if The plugin is not found in the installed plugins list, then the environment is not affected by this specific vulnerability
  2. Identify the installed version
    In the WordPress plugins list, locate the version number displayed beneath the plugin name 'Element Pack' or check the plugin's main file header via FTP/file manager at wp-content/plugins/bdthemes-element-pack-lite/ or wp-content/plugins/bdthemes-element-pack/
    Affected if Unable to determine the version - further investigation needed
  3. Compare version against affected range
    Compare the installed version number to the affected range: any version below 5.5.4 is vulnerable (e.g., 5.5.3, 5.5.0, 5.0.0, etc.)
    Affected if Installed version is 5.5.3 or lower - the environment is within the affected version range
  4. Verify plugin is active with Elementor
    Confirm the Element Pack plugin status is 'Active' and that the Elementor page builder plugin is also installed and active, as this vulnerability affects Elementor addon components
    Affected if Plugin is active and Elementor is in use - the attack surface exists for this stored XSS vulnerability

Environment is affected if BdThemes Element Pack is installed, active, running Elementor, and the installed version is below 5.5.4

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.5.4 or later
Fixed in 5.5.4
Interim mitigation

Update Element Pack Elementor Addons to the latest patched version once available. As a temporary measure, disable or remove the plugin until a fix is released. Review and sanitize all user-supplied input fields within the plugin.

Recommended fix High confidence

5.5.4

  1. Upgrade Element Pack Elementor Addons to version 5.5.4 or later

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
  • 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-30185 — 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-30185 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