dbcve.org
Website BuilderWordPress extension · Elementor

CVE-2024-2120

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-27
Fix available
A fix is available. Upgrade to 3.20.2 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 Pro plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Post Navigation widget in all versions up to, and including, 3.20.1 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 Elementor Website Builder Pro plugin for WordPress is vulnerable to Stored Cross-Site Scripting in the Post Navigation widget. Authenticated attackers with contributor-level or higher permissions can inject malicious JavaScript through unsanitized user-supplied attributes, which then executes whenever users access affected pages.

MitigationUpdate Elementor Website Builder Pro to version 3.20.2 or later. Until updated, restrict contributor-level permissions or disable the Post Navigation widget on sites where feasible.

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.2

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. Identify installed Elementor version
    Navigate to WordPress Dashboard > Plugins > Installed Plugins, locate 'Elementor Website Builder', and note the installed version number
    Affected if The installed version is earlier than 3.20.2
  2. Verify Post Navigation widget usage
    In the WordPress admin, go to Pages or Posts and check if any content was created or edited using Elementor with the Post Navigation widget present on any pages
    Affected if The Post Navigation widget is present on any published pages or posts on the site
  3. Confirm contributor-level user accounts exist
    Go to WordPress Dashboard > Users and review the user list to identify any accounts with the 'Contributor' role or higher (Author, Editor, Administrator)
    Affected if At least one user account with contributor-level or higher permissions exists on the site
  4. Inspect for unsanitized widget attributes
    Edit a page using Elementor, select the Post Navigation widget, and examine the widget settings panel for any user-supplied fields (such as labels or navigation text) that may contain custom values
    Affected if Custom text fields in the Post Navigation widget accept input without visible sanitization or validation in the UI

The site is affected if Elementor version is below 3.20.2 AND the Post Navigation widget is in use AND at least one contributor-level or higher user account exists on the site.

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.2 or later
Fixed in 3.20.2
Interim mitigation

Update Elementor Website Builder Pro to version 3.20.2 or later. Until updated, restrict contributor-level permissions or disable the Post Navigation widget on sites where feasible.

Recommended fix High confidence

3.20.2

  1. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  2. Locate the Elementor Website Builder Pro plugin
  3. Click 'Update Now' to update to version 3.20.2 or later
  4. Verify the update was successful by checking the plugin version in the plugins list

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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