dbcve.org
Website BuilderWordPress extension · Elementor

CVE-2024-2117

MEDIUM · 5.4 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to 3.20.3 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 plugin's Path Widget in all versions up to, and including, 3.20.2 due to insufficient 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 Elementor Website Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting (XSS) in its Path Widget. The vulnerability exists due to insufficient output escaping on user-supplied attributes within the Path Widget, allowing authenticated attackers with contributor-level or higher permissions to inject malicious JavaScript that executes when users access affected pages.

MitigationUpdate the Elementor Website Builder plugin to version 3.20.3 or later to patch the vulnerability. If immediate updating is not possible, consider restricting content editing permissions or temporarily disabling the Elementor 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
Website BuilderWordPress extension
Affected:< 3.20.3

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 plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Elementor Website Builder and note the version number displayed. Alternatively, check the version in the plugin files (typically in elementor.php or readme.txt within the plugin directory).
    Affected if The installed version is lower than 3.20.3 (e.g., 3.20.2, 3.19.0, etc.)
  2. Identify Path Widget usage
    Review pages and posts created with Elementor for the presence of the Path Widget. In Elementor editor, search for 'Path' in the widget panel or inspect existing pages for the elementor-element-type-path class or similar Path Widget markers in the page source.
    Affected if The Path Widget is present and actively used on any published page or post on the site.
  3. Verify contributor-level user accounts
    In WordPress admin, go to Users > All Users and review the role assigned to each user. Look for users with Contributor, Author, Editor, or Administrator roles, as these all have permissions equal to or higher than Contributor.
    Affected if There are one or more user accounts with Contributor-level permissions or higher who have access to edit content via Elementor.

You are affected if your Elementor plugin version is below 3.20.3 AND the Path Widget is in use on your site AND there are users with contributor-level or higher permissions who can edit 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 3.20.3 or later
Fixed in 3.20.3
Interim mitigation

Update the Elementor Website Builder plugin to version 3.20.3 or later to patch the vulnerability. If immediate updating is not possible, consider restricting content editing permissions or temporarily disabling the Elementor plugin.

Recommended fix High confidence

Elementor Website Builder 3.20.3

  1. Backup your WordPress site before making any changes
  2. Navigate to WordPress admin > Plugins > Installed Plugins
  3. Find Elementor Website Builder and click 'Update Now' to upgrade to version 3.20.3 or later
  4. Alternatively, download version 3.20.3 from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  5. After updating, verify the plugin version shows 3.20.3 or higher in the plugins list
  6. Clear any caching plugins or server-side caches to ensure the fix takes effect

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
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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