dbcve.org
Exclusive Addons For ElementorWordPress extension · Exclusiveaddons

CVE-2024-30177

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-27
Fix available
A fix is available. Upgrade to 2.6.9 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Exclusive Addons Exclusive Addons Elementor allows Stored XSS.This issue affects Exclusive Addons Elementor: from n/a through 2.6.8.

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 Stored Cross-Site Scripting (XSS) vulnerability exists in Exclusive Addons Elementor plugin versions up to 2.6.8. The vulnerability allows malicious JavaScript code to be injected through plugin inputs and stored in the database, executing when other users view affected pages in the Elementor page builder.

MitigationUpdate Exclusive Addons Elementor to the latest version after the vendor releases a patch. Until then, restrict access to the WordPress admin dashboard and Elementor editor to trusted users only.

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
Exclusive Addons For ElementorWordPress extension
Affected:< 2.6.9

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 Exclusive Addons For Elementor is installed
    In WordPress admin, go to Plugins > Installed Plugins and search for 'Exclusive Addons For Elementor' or check the plugins directory for the exclusive-addons-for-elementor folder
    Affected if Plugin is present in the installation
  2. Check if the plugin is active
    In Plugins > Installed Plugins, confirm the Exclusive Addons For Elementor plugin shows as 'Active'
    Affected if Plugin is active and vulnerable version is installed
  3. Identify installed version number
    In Plugins > Installed Plugins, click on the plugin name or view its details to find the version number displayed under the plugin name
    Affected if Version is 2.6.8 or lower (versions below 2.6.9 are affected)
  4. Inspect Elementor content for suspicious stored data
    Review saved Elementor templates, pages, and posts that use Exclusive Addons widgets. Check for unexpected script tags, event handlers (onclick, onerror, etc.), or unfamiliar JavaScript URLs in text fields, URLs, or custom code widgets
    Affected if Malicious script content is found stored in Elementor content using the plugin

The environment is affected if Exclusive Addons For Elementor plugin is active and the installed version is below 2.6.9.

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.6.9 or later
Fixed in 2.6.9
Interim mitigation

Update Exclusive Addons Elementor to the latest version after the vendor releases a patch. Until then, restrict access to the WordPress admin dashboard and Elementor editor to trusted users only.

Recommended fix High confidence

2.6.9

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Exclusive Addons for Elementor' in the plugin list
  4. Check if the current version is below 2.6.9
  5. If vulnerable, click 'Update Now' to upgrade to version 2.6.9
  6. After updating, verify the new version is 2.6.9

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

Fix this in Exclusive Addons For Elementor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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