dbcve.org
Essential Addons For ElementorWordPress extension · Wpdeveloper

CVE-2025-39590

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-16
Fix available
A fix is available. Upgrade to 6.1.10 or later.
See remediation →
69/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 WPDeveloper Essential Addons for Elementor essential-addons-for-elementor-lite allows Stored XSS.This issue affects Essential Addons for Elementor: from n/a through <= 6.1.9.

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

Stored XSS vulnerability in Essential Addons for Elementor lite plugin (versions <= 6.1.9) allows attackers to inject malicious scripts through improperly sanitized user input that gets stored and executed when other users view the affected page.

MitigationUpdate to the latest version of Essential Addons for Elementor when available; review and sanitize any custom code or third-party Elementor widgets; implement Content Security Policy headers as defense-in-depth.

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
Essential Addons For ElementorWordPress extension
Affected:< 6.1.10

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
Low

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

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 the installed version of Essential Addons for Elementor
    Navigate to WordPress admin > Plugins > Installed Plugins > Essential Addons for Elementor and note the version number displayed
    Affected if The displayed version is 6.1.9 or lower (any version below 6.1.10)
  2. Identify pages using Essential Addons widgets with user input
    In Elementor editor, review pages that contain Essential Addons widgets (such as forms, login/register widgets, or any widget accepting user-submitted content) and check if they accept and store user input
    Affected if Any Essential Addons widget that stores and displays user input back to visitors is in use on published pages
  3. Inspect stored content in affected widgets for script injection
    View the page source or use browser developer tools to examine the HTML rendered by Essential Addons widgets. Look for unsanitized HTML attributes, script tags, or event handlers within the widget output
    Affected if Raw script tags, javascript: URIs, or event handler attributes (onclick, onerror, onload, etc.) appear in the rendered HTML where user input was submitted
  4. Check Elementor revision history for suspicious input patterns
    In Elementor, go to the affected page > Revisions > examine recent changes for any unusual script tags or HTML injected into Essential Addons widget fields
    Affected if Revision history shows malicious script content was saved and is being stored in the database

You are affected if the plugin version is 6.1.9 or lower AND any Essential Addons widget that stores user input is in use on your site, with unsanitized script content appearing in the rendered output.

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

Update to the latest version of Essential Addons for Elementor when available; review and sanitize any custom code or third-party Elementor widgets; implement Content Security Policy headers as defense-in-depth.

Recommended fix High confidence

Essential Addons for Elementor 6.1.10

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find 'Essential Addons for Elementor' in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 6.1.10 or later
  5. 5. Alternatively, go to Dashboard > Updates and apply available updates
  6. 6. After updating, verify the plugin version shows 6.1.10 or higher under Plugins > Installed Plugins

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

Fix this in Essential Addons For Elementor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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