dbcve.org
Website BuilderWordPress extension · Elementor

CVE-2024-4619

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-21
Fix available
A fix is available. Upgrade to 3.21.5 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 DOM-Based Stored Cross-Site Scripting via the ‘hover_animation’ parameter in versions up to, and including, 3.21.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level permissions 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 versions up to 3.21.5 contains a stored DOM-based Cross-Site Scripting vulnerability in the 'hover_animation' parameter. Authenticated attackers with contributor-level permissions can inject malicious JavaScript through insufficient input sanitization and improper output escaping, which executes when users view injected pages.

MitigationUpdate the Elementor plugin to version 3.22.0 or later. Until then, restrict contributor-level permissions and audit users with contributor access.

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

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 plugin installation
    Log in to WordPress admin, navigate to Plugins > Installed Plugins, locate 'Elementor Website Builder' and note the installed version number
    Affected if The plugin is installed and the version is below 3.21.5 (versions 3.21.5 and earlier are vulnerable)
  2. Confirm the exact version number
    Compare the installed version shown in the plugins list against the affected range: any version less than 3.21.5 is vulnerable
    Affected if Installed version is less than 3.21.5
  3. Identify contributor-level users
    In WordPress admin, go to Users > All Users, review the list for any accounts assigned the Contributor role
    Affected if Contributor users exist in the WordPress installation
  4. Audit Elementor-created content for suspicious scripts
    Inspect pages and posts created using the Elementor editor. View the page source or use browser dev tools to examine for unexpected script tags, inline JavaScript, or event handlers in elements that may have been set via the hover_animation parameter
    Affected if Any Elementor content contains injected JavaScript that was not intentionally added by an administrator
  5. Check for unauthorized contributor content
    In WordPress admin, review Posts and Pages authored by contributor users. Look for published or pending review content containing unusual HTML, script tags, or onclick/onmouseover attributes
    Affected if Contributor-authored content exists and contains unexpected script injections

The environment is affected if Elementor plugin version is below 3.21.5 AND contributor-level users have access to create or 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.21.5 or later
Fixed in 3.21.5
Interim mitigation

Update the Elementor plugin to version 3.22.0 or later. Until then, restrict contributor-level permissions and audit users with contributor access.

Recommended fix High confidence

Elementor Website Builder version 3.21.6 or later

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find the Elementor Website Builder plugin
  5. 5. If an update is available, click 'Update Now' to upgrade to version 3.21.6 or later
  6. 6. Alternatively, download the latest version from wordpress.org/plugins/elementor/ and upload it manually
  7. 7. Verify the installed version is 3.21.6 or higher after updating
  8. 8. Test that the hover animation feature still functions correctly on pages

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

Fix this in Website Builder Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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