dbcve.org
Elementor ProWordPress extension · Elementor

CVE-2024-1364

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 widget's custom_id 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 versions up to 3.20.1 contains a stored XSS vulnerability in the widget's custom_id attribute. Authenticated users with contributor-level or higher permissions can inject arbitrary JavaScript through insufficiently sanitized input, which executes when other users access the affected pages.

MitigationUpgrade Elementor Website Builder Pro to version 3.20.2 or later. The fix requires implementing proper input sanitization (such as sanitize_html_class) and output escaping (such as esc_attr) on the custom_id attribute throughout the 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
Elementor ProWordPress 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. Verify Elementor Pro is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Elementor Website Builder Pro'. Note the installed version number.
    Affected if The plugin version shown is less than 3.20.2 (for example, 3.20.1, 3.20.0, or earlier)
  2. Confirm the vulnerability scope
    The flaw exists in the widget's custom_id attribute. This attribute is available when editing any Elementor widget (such as containers, sections, or individual widgets) under the Advanced tab in the Elementor editor.
    Affected if The custom_id field accepts user input without proper sanitization in the installed version
  3. Identify users with contributor-level access
    Go to WordPress Users > All Users and review user roles. Contributor role and higher (Contributor, Author, Editor, Administrator) can access the Elementor editor and modify widgets.
    Affected if There are WordPress user accounts with Contributor, Author, Editor, or Administrator roles who have access to the Elementor editor
  4. Inspect saved custom_id values in the database
    Query the WordPress postmeta table (wp_postmeta) for meta_key containing 'custom_id' or examine Elementor data stored in post content for any custom_id attributes with suspicious values.
    Affected if Any custom_id values in the database contain script tags, event handlers, or other XSS payloads
  5. Review recent Elementor editor activity
    Check WordPress revision history or activity logs for recent edits made by contributor-level or higher users to Elementor-managed pages.
    Affected if Pages were recently edited using the Elementor editor by users with contributor-level or higher permissions

You are affected if Elementor Website Builder Pro version is below 3.20.2 and you have users with contributor-level or higher permissions who can access the Elementor editor and inject malicious code into the custom_id attribute.

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

Upgrade Elementor Website Builder Pro to version 3.20.2 or later. The fix requires implementing proper input sanitization (such as sanitize_html_class) and output escaping (such as esc_attr) on the custom_id attribute throughout the plugin.

Recommended fix High confidence

Elementor Pro 3.20.2

  1. 1. Back up your WordPress database and files before performing any updates
  2. 2. Log in to your WordPress admin dashboard
  3. 3. Navigate to Plugins > Installed Plugins
  4. 4. Locate Elementor Pro in the plugin list
  5. 5. If an update is available, click 'Update Now' to upgrade to version 3.20.2
  6. 6. Alternatively, upload Elementor Pro version 3.20.2 manually via Plugins > Add New > Upload Plugin
  7. 7. After updating, clear any caching plugins or server-side caches
  8. 8. Test that the Elementor editor loads correctly and existing pages render properly

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

Fix this in Elementor Pro Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.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-1364 — 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-1364 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