dbcve.org
Exclusive Addons For ElementorWordPress extension · Exclusiveaddons

CVE-2024-32557

MEDIUM · 5.4 CVSS v3.1 Published 2024-04-16
Fix available
A fix is available. Upgrade to after 2.6.9.2 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.9.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

Stored XSS vulnerability in Exclusive Addons Elementor plugin allows authenticated attackers to inject malicious JavaScript into pages built with the plugin. The injected payload persists in the database and executes in victims' browsers when they view affected pages.

MitigationUpdate Exclusive Addons Elementor to the latest patched version. If update unavailable, disable the plugin. Review recent admin activity for signs of exploitation.

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

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. Check plugin version
    Go to WordPress admin > Plugins > Installed Plugins > Exclusive Addons for Elementor and note the version number displayed
    Affected if The installed version is 2.6.9.2 or lower
  2. Identify pages built with Exclusive Addons
    In WordPress admin, go to Pages or Posts and look for entries that were created using the Elementor editor and include Exclusive Addons widgets
    Affected if The site uses pages or posts that leverage Exclusive Addons Elementor widgets
  3. Inspect page content for injected scripts
    Access the WordPress database (via phpMyAdmin or wp CLI) and query the wp_posts table for script tags or javascript: URIs in post_content where post_type is 'page' or 'post'
    Affected if The post_content field contains unsanitized script tags, iframe tags, or javascript: protocol handlers that were not intentionally added
  4. Review Elementor custom CSS or theme settings
    Check the WordPress Customizer > Additional CSS or Elementor page settings for any unexpected script injections or encoded content
    Affected if Unexpected JavaScript code or encoded payloads are present in these configuration areas

If the installed version is 2.6.9.2 or lower AND the site uses Exclusive Addons widgets in pages, inspect the database for any unauthorized script tags in post content to confirm exploitation.

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 a release after 2.6.9.2
Interim mitigation

Update Exclusive Addons Elementor to the latest patched version. If update unavailable, disable the plugin. Review recent admin activity for signs of exploitation.

Recommended fix Moderate confidence

Exclusive Addons For Elementor version 2.6.9.3 or latest available version

  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 an update is available for the plugin
  5. If an update is available, click 'Update Now' to install the latest version
  6. After updating, verify the plugin version shows a version higher than 2.6.9.2
  7. Clear any caching plugins or server-side caches to ensure the patched code is served

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.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-2024-32557 — 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-32557 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