dbcve.org
Exclusive Addons For ElementorWordPress extension · Exclusiveaddons

CVE-2024-2751

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-02
Fix available
A fix is available. Upgrade to 2.6.9.3 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
The Exclusive Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘exad_infobox_animating_mask_style’ parameter in all versions up to, and including, 2.6.9.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor access or higher, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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

The Exclusive Addons for Elementor WordPress plugin is vulnerable to stored Cross-Site Scripting (XSS) via the 'exad_infobox_animating_mask_style' parameter in versions up to 2.6.9.2. Authenticated attackers with contributor-level access or higher can inject malicious JavaScript through insufficient input sanitization, which executes when other users access the compromised pages due to inadequate output escaping.

MitigationUpdate the plugin to version 2.6.9.3 or later. If immediate update is not possible, implement input sanitization using WordPress sanitization functions (e.g., sanitize_text_field) and ensure proper output escaping using functions like esc_attr() or esc_html() when rendering the affected parameter.

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.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
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 plugin installation
    Check if Exclusive Addons for Elementor is installed by reviewing the WordPress plugins directory at /wp-content/plugins/ or via the WordPress admin dashboard under Plugins
    Affected if The plugin is present in the installation
  2. Check installed version
    Locate the main plugin file (typically exclusive-addons-for-elementor.php) and read the Version header in the plugin comments, or check via WordPress admin under Plugins > Installed Plugins
    Affected if The version is below 2.6.9.3 (any version from 2.6.9.2 or earlier)
  3. Identify use of Infobox element
    Review pages/posts created with Elementor that use the Exclusive Addons Infobox widget, as the vulnerable parameter 'exad_infobox_animating_mask_style' is specific to this widget
    Affected if The Infobox element from Exclusive Addons is in use on the site
  4. Inspect stored parameter value
    Examine the post meta or Elementor data where the 'exad_infobox_animating_mask_style' parameter is stored - this can be found in the post meta table (wp_postmeta) with meta_key containing the Infobox settings, or by inspecting the Elementor page data in the database
    Affected if The 'exad_infobox_animating_mask_style' parameter contains unsanitized/custom JavaScript values or appears in database records

A user is affected if Exclusive Addons for Elementor is installed at a version below 2.6.9.3 AND the Infobox widget with the animating_mask_style parameter is in use on any published page.

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

Update the plugin to version 2.6.9.3 or later. If immediate update is not possible, implement input sanitization using WordPress sanitization functions (e.g., sanitize_text_field) and ensure proper output escaping using functions like esc_attr() or esc_html() when rendering the affected parameter.

Recommended fix High confidence

Exclusive Addons For Elementor version 2.6.9.3

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Exclusive Addons For Elementor' in the plugin list
  4. Click 'Update Now' if an update is available, or manually update to version 2.6.9.3
  5. Verify the plugin version shows 2.6.9.3 or later after updating
  6. Clear any site caches (if using caching plugins) to ensure the patched version 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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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