dbcve.org
Elementor ProWordPress extension · Elementor

CVE-2024-35656

MEDIUM · 6.1 CVSS v3.1 Published 2024-07-22
Fix available
A fix is available. Upgrade to 3.21.3 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 (XSS or 'Cross-site Scripting') vulnerability in Elementor Elementor Pro allows Reflected XSS.This issue affects Elementor Pro: from n/a through 3.21.2.

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

Reflected XSS vulnerability in Elementor Pro allows attackers to inject malicious scripts through unsanitized input that gets reflected in web page generation. The flaw exists in versions up to 3.21.2 and could allow session hijacking or phishing via crafted URLs.

MitigationUpdate Elementor Pro to the latest version beyond 3.21.2 which contains the patch for this vulnerability.

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

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm Elementor Pro is installed
    Check the WordPress plugin directory or inspect the file system for the Elementor Pro plugin files, typically found in /wp-content/plugins/elementor-pro/
    Affected if The plugin directory does not exist or Elementor Pro is not present on the system
  2. Identify installed version of Elementor Pro
    Access the WordPress admin dashboard, navigate to Plugins, find Elementor Pro in the list, and read the version number displayed under the plugin name
    Affected if The version number displayed is less than 3.21.3 (for example, 3.21.2, 3.21.1, 3.20.0, etc.)
  3. Verify Elementor Pro is active on the site
    In the WordPress admin under Plugins, confirm that Elementor Pro shows as Active rather than deactivated or inactive
    Affected if Elementor Pro is active and running on the WordPress site
  4. Check if site accepts URL parameters that Elementor processes
    Inspect forms, search functions, or URL parameters on pages built with Elementor that accept user input and reflect it back in the response
    Affected if The site uses Elementor widgets or features that reflect user-supplied input (such as search, form submissions, or URL-based parameters) without sanitization

The environment is affected if Elementor Pro is installed and active with a version lower than 3.21.3, and the site uses features that reflect user input in web page generation.

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.3 or later
Fixed in 3.21.3
Interim mitigation

Update Elementor Pro to the latest version beyond 3.21.2 which contains the patch for this vulnerability.

Recommended fix High confidence

Elementor Pro 3.21.3

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find Elementor Pro in the plugin list
  4. Check if the current version is below 3.21.3
  5. If an update is available, click 'Update Now' to upgrade Elementor Pro to version 3.21.3 or later
  6. After updating, verify the new version number in the Plugins list to confirm the upgrade was successful
  7. Clear any caching plugins or server-side caches to ensure the patched version is fully deployed

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

Fix this in Elementor Pro Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,370
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,192.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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