dbcve.org
Element PackWordPress extension · Bdthemes

CVE-2024-2455

MEDIUM · 5.4 CVSS v3.1 Published 2024-08-01
Fix available
A fix is available. Upgrade to after 7.9.0 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 - Addon for Elementor Page Builder WordPress Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the widget wrapper link URL in all versions up to, and including, 7.9.0 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions 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 plugin for WordPress versions up to 7.9.0 contains a stored XSS vulnerability in the widget wrapper link URL functionality. Authenticated users with contributor-level or higher permissions can inject arbitrary JavaScript through unsanitized user-supplied attributes that are not properly escaped when rendered, causing the malicious script to execute whenever users access the affected pages.

MitigationUpdate the Element Pack plugin to a version newer than 7.9.0 which contains the security fix, or implement proper input sanitization (e.g., esc_url()) and output escaping on user-supplied URL attributes in the affected widget code.

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:<= 7.9.0

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 is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Element Pack' in the list. Note if it is active or inactive.
    Affected if The Element Pack plugin is installed and active on the WordPress site
  2. Check installed Element Pack version
    On the Plugins page, find the Element Pack entry and note the version number displayed below the plugin name. Compare this version to the affected range: any version <= 7.9.0 is vulnerable.
    Affected if The installed version is 7.9.0 or lower
  3. Identify use of widget wrapper link feature
    Review pages and posts where Element Pack widgets are used. Check each Element Pack widget settings for a 'Wrapper Link' or 'Link URL' field in the widget configuration panel.
    Affected if Any Element Pack widget has a wrapper link or link URL field configured with user-supplied input
  4. Check user role permissions
    Go to Users > All Users in WordPress admin. Review which users have contributor-level or higher roles (Contributor, Author, Editor, Administrator).
    Affected if Any user account has contributor-level or higher permissions and can edit content with Element Pack widgets
  5. Inspect for injected scripts in widget output
    View the source code of pages containing Element Pack widgets with wrapper links. Look for script tags or javascript: URLs in href attributes of widget wrapper links.
    Affected if The rendered HTML contains unsanitized JavaScript in link href attributes on pages with Element Pack widgets

The site is affected if Element Pack version 7.9.0 or lower is installed, the plugin is active, and any widget with wrapper link functionality is in use by users with contributor-level access or higher.

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 a release after 7.9.0
Interim mitigation

Update the Element Pack plugin to a version newer than 7.9.0 which contains the security fix, or implement proper input sanitization (e.g., esc_url()) and output escaping on user-supplied URL attributes in the affected widget code.

Recommended fix Moderate confidence

Latest version after 7.9.0 (check WordPress plugin repository for current release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Element Pack - Addon for Elementor Page Builder'
  4. If an update is available, click 'Update Now'
  5. Alternatively, download the latest version from WordPress.org or the Element Pack official site
  6. Deactivate and re-activate the plugin if needed after updating

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