dbcve.org
Website BuilderWordPress extension · Elementor

CVE-2020-7109

CRITICAL · 9.8 CVSS v3.1 Published 2020-01-22
Fix available
A fix is available. Upgrade to 2.8.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
The Elementor Page Builder plugin before 2.8.4 for WordPress does not sanitize data during creation of a new template.

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

The Elementor Page Builder plugin before version 2.8.4 lacks proper data sanitization when creating new templates, allowing injection of malicious scripts. This is likely a stored XSS vulnerability where unsanitized template data is saved to the database and executed when viewed by other users or administrators.

MitigationUpdate Elementor Page Builder plugin to version 2.8.4 or later. If immediate update is not possible, restrict template creation permissions to trusted administrators only until the patch can be applied.

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:< 2.8.4

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and locate 'Elementor Website Builder' in the list
    Affected if Elementor Website Builder plugin is not present in the plugins list, then the vulnerability does not apply
  2. Determine installed Elementor version
    In the plugins list, look for the version number displayed under the Elementor plugin name, or click on the plugin and view the details panel
    Affected if The displayed version number is less than 2.8.4 (for example, 2.8.3, 2.8.2, 2.8.1, etc.)
  3. Confirm template creation capability exists
    Navigate to Templates > Saved Templates in the WordPress admin sidebar and verify the page loads with options to create or import templates
    Affected if The Saved Templates menu item exists and is accessible, indicating the template feature is enabled and the vulnerable code path is present
  4. Inspect existing templates for suspicious content
    In Templates > Saved Templates, review each saved template and check the template content/source for unusual script tags, event handlers, or encoded payloads that may indicate exploitation
    Affected if Any template contains unsanitized script tags, javascript: URIs, or XSS payload patterns in template content or metadata

If Elementor Website Builder is installed with a version lower than 2.8.4 and the template creation feature is accessible, the environment is likely affected by this stored XSS vulnerability.

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 2.8.4 or later
Fixed in 2.8.4
Interim mitigation

Update Elementor Page Builder plugin to version 2.8.4 or later. If immediate update is not possible, restrict template creation permissions to trusted administrators only until the patch can be applied.

Recommended fix High confidence

Elementor Page Builder version 2.8.4

  1. Backup your WordPress site before performing any updates
  2. Log in to your WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Locate the Elementor Page Builder plugin in the list
  5. Check the current version number displayed below the plugin name
  6. If the installed version is below 2.8.4, click the 'Update Now' link that appears next to the plugin, or go to Dashboard > Updates and update Elementor there
  7. After the update completes, verify the new version is 2.8.4 or higher by refreshing the Plugins page
  8. Test that the Elementor editor and template creation functionality work correctly

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

Fix this in Website Builder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.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-2020-7109 — 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-2020-7109 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