dbcve.org
Website BuilderWordPress extension · Elementor

CVE-2024-8236

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-26
Fix available
A fix is available. Upgrade to after 3.25.7 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 Elementor Website Builder – More than Just a Page Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘url’ parameter of the Icon widget in all versions up to, and including, 3.25.7 due to insufficient input sanitization and output escaping. 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 Elementor Website Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting (XSS) in the Icon widget's 'url' parameter. Insufficient input sanitization on input and lack of output escaping allows authenticated users with Contributor-level permissions or higher to inject malicious JavaScript that executes whenever users access the compromised page.

MitigationUpdate Elementor Website Builder plugin to version 3.25.8 or later to remediate this vulnerability.

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
Website BuilderWordPress extension
Affected:<= 3.25.7

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. Check installed Elementor version
    Go to WordPress Dashboard > Plugins > Elementor Website Builder and note the version number displayed, or use WP-CLI: wp plugin list --name=elementor
    Affected if The installed version is 3.25.7 or earlier (any version <= 3.25.7)
  2. Verify Contributor-level or higher users exist
    Go to WordPress Dashboard > Users and review user roles, or use WP-CLI: wp user list --role=contributor
    Affected if Any user account has Contributor, Author, Editor, or Administrator role (these roles can access the Elementor editor)
  3. Identify Icon widgets with URL configured
    Review pages/posts edited with Elementor that contain Icon widgets. Check the widget settings panel for any URL/link assigned to the icon, or query the WordPress database: SELECT p.ID, p.post_title FROM wp_posts p JOIN wp_postmeta m ON p.ID = m.post_id WHERE m.meta_key LIKE '%elementor_data%' AND m.meta_value LIKE '%"url":"%'
    Affected if Any Icon widget has a URL/links configured in any published Elementor-edited page or post

A user is affected if they have Elementor Website Builder version 3.25.7 or earlier AND have users with Contributor-level or higher access AND have Icon widgets with URLs configured in their content.

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 3.25.7
Interim mitigation

Update Elementor Website Builder plugin to version 3.25.8 or later to remediate this vulnerability.

Recommended fix High confidence

3.25.8 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find Elementor Website Builder plugin
  4. Click 'Update Now' if an update is available, or manually update to version 3.25.8 or later
  5. Verify the update was successful

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

Fix this in Website Builder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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