dbcve.org
Element PackWordPress extension · Bdthemes

CVE-2024-30496

HIGH · 8.8 CVSS v3.1 Published 2024-03-29
Fix available
A fix is available. Upgrade to 5.5.4 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 Special Elements used in an SQL Command ('SQL Injection') vulnerability in BdThemes Element Pack Elementor Addons.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

SQL injection vulnerability in BdThemes Element Pack Elementor Addons allows attackers to inject malicious SQL commands through unsanitized user inputs in affected versions up to and including 5.5.3. The vulnerability stems from improper neutralization of special elements in SQL queries, potentially allowing unauthorized database access, data exfiltration, or modification.

MitigationUpdate Element Pack Elementor Addons to the latest version (5.5.4 or later) which contains the patched code. If immediate update is not possible, disable the affected plugin or implement WAF rules as a temporary compensating control.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Locate Element Pack plugin installation
    Access your WordPress site via FTP or file manager and navigate to /wp-content/plugins/element-pack/ or check the WordPress Plugins admin page for 'Element Pack Elementor Addons'
    Affected if The plugin directory or listing exists on the system
  2. Determine installed version
    In WordPress admin, go to Plugins > Installed Plugins > Element Pack and view the version number displayed, or check the 'readme.txt' or 'element-pack.php' file in the plugin directory for the 'Version' header
    Affected if The displayed version is 5.5.3 or lower (any version below 5.5.4)
  3. Verify the vulnerable code exists
    If you have file access, search the plugin directory for potential SQL query handlers that process user input without sanitization. Look for files containing '$wpdb->prepare', '$wpdb->query', or direct SQL concatenation with $_GET, $_POST, or $_REQUEST parameters
    Affected if The plugin contains code that passes unsanitized user input directly into SQL queries

If Element Pack is installed with version 5.5.3 or below, the environment is affected by this SQL injection vulnerability and should be updated to 5.5.4 or later.

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 version (5.5.4 or later) which contains the patched code. If immediate update is not possible, disable the affected plugin or implement WAF rules as a temporary compensating control.

Recommended fix High confidence

Element Pack version 5.5.4 or latest available

  1. In the WordPress admin dashboard, navigate to Plugins > Installed Plugins
  2. Locate 'Element Pack - Elementor Addons' in the plugin list
  3. If an update is available, click 'Update Now' to upgrade to version 5.5.4 or later
  4. Alternatively, download version 5.5.4 or the latest version from the official WordPress repository or BdThemes website
  5. Deactivate and delete the current version, then upload and install the new version
  6. After upgrade, clear any caching plugins and verify the plugin functions correctly

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
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,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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