dbcve.org
Website BuilderWordPress extension · Elementor

CVE-2024-37437

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-09
Fix available
A fix is available. Upgrade to 3.22.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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Elementor Elementor Website Builder elementor.This issue affects Elementor Website Builder: from n/a through <= 3.22.1.

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 · moderate confidence

Cross-site scripting (XSS) vulnerability in Elementor Website Builder allows attackers to inject malicious JavaScript into web pages through improper input neutralization. This affects versions through 3.22.1, potentially compromising other users who view injected content.

MitigationUpdate to the latest patched version of Elementor Website Builder that implements proper input sanitization and output encoding.

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.22.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 Elementor version installed
    Log into WordPress admin, go to Plugins > Installed Plugins > Elementor Website Builder, and read the version number from the plugin details
    Affected if The version listed is lower than 3.22.2 (for example, 3.22.1, 3.22.0, 3.21.x, etc.)
  2. Verify WordPress is running Elementor
    Check the wp-content/plugins/elementor directory exists and contains the main elementor.php file, or query the WordPress options table for the active_plugins setting
    Affected if Elementor plugin is active on the WordPress installation
  3. Confirm the site uses Elementor for published content
    Inspect source code of live pages for 'elementor' CSS classes (such as elementor-section, elementor-widget) or check pages in the WordPress admin under Pages > All Pages for those edited with Elementor
    Affected if Public-facing pages are built or edited using the Elementor editor
  4. Check for user-submitted content features
    Review installed Elementor widgets and any third-party Elementor add-ons for form widgets, comment widgets, or user-generated content widgets that accept and display visitor input
    Affected if The site uses widgets or forms that accept and display user input without additional sanitization layers

You are affected if Elementor Website Builder version is below 3.22.2 AND the site uses Elementor to publish pages that display user-submitted 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.22.2 or later
Fixed in 3.22.2
Interim mitigation

Update to the latest patched version of Elementor Website Builder that implements proper input sanitization and output encoding.

Recommended fix High confidence

3.22.2

  1. Create a complete backup of your WordPress site, including database and files
  2. Update Elementor Website Builder to version 3.22.2 or later through WordPress admin > Plugins or Dashboard > Updates
  3. Verify the update was successful by checking the Elementor version in WordPress admin > Elementor > About
  4. Test critical website functionality to ensure the update did not break existing pages

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

Fix this in Website Builder Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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