dbcve.org
Website BuilderWordPress extension · Elementor

CVE-2024-24934

HIGH · 8.1 CVSS v3.1 Published 2024-05-17
Fix available
A fix is available. Upgrade to 3.19.1 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Elementor Elementor Website Builder allows Manipulating Web Input to File System Calls.This issue affects Elementor Website Builder: from n/a through 3.19.0.

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

A path traversal vulnerability in Elementor Website Builder allows attackers to manipulate web input to access files outside the intended directory. This occurs due to improper validation of file paths in user-supplied input before using them in file system operations.

MitigationUpgrade Elementor Website Builder to version 3.19.1 or later. If immediate patching is not possible, implement web application firewall rules to block directory traversal patterns (e.g., ../ sequences) in user inputs.

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

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
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

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 Website Builder is installed
    Check your WordPress site under Plugins > Installed Plugins, or inspect wp-content/plugins/elementor/elementor.php for the plugin header, or run: wp plugin list --status=active --format=csv
    Affected if Elementor Website Builder is present in the WordPress installation
  2. Determine the installed Elementor version
    Check the Elementor version number in the plugin admin page, in the plugin header comment of elementor.php, or in the readme.txt file within the plugin directory
    Affected if The version number is lower than 3.19.1 (e.g., 3.19.0, 3.18.x, etc.)
  3. Confirm Elementor is active on the site
    Verify the plugin status shows 'Active' in WordPress admin under Plugins, or check via WP-CLI: wp plugin status elementor
    Affected if Elementor is installed and active (inactive plugins with this vulnerability still warrant attention but the exploit path differs)

You are affected if Elementor Website Builder is installed and active with a version lower than 3.19.1, as the vulnerable code path processes user-supplied file path input without proper validation.

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.19.1 or later
Fixed in 3.19.1
Interim mitigation

Upgrade Elementor Website Builder to version 3.19.1 or later. If immediate patching is not possible, implement web application firewall rules to block directory traversal patterns (e.g., ../ sequences) in user inputs.

Recommended fix High confidence

Elementor Website Builder version 3.19.1

  1. Log in to the WordPress admin dashboard where Elementor Website Builder is installed
  2. Navigate to Plugins > Installed Plugins
  3. Locate Elementor Website Builder in the plugin list
  4. Check the current installed version to confirm it is below 3.19.1
  5. Update the plugin to version 3.19.1 or later
  6. Verify the update was successful by confirming the new version number
  7. Test the website functionality to ensure the update did not break existing features

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-24934 — 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-24934 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