dbcve.org
Exclusive Addons For ElementorWordPress extension · Exclusiveaddons

CVE-2024-33914

CRITICAL · 9.8 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 2.6.9.2 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
Missing Authorization vulnerability in Exclusive Addons Exclusive Addons Elementor.This issue affects Exclusive Addons Elementor: from n/a through 2.6.9.1.

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

Missing authorization vulnerability in Exclusive Addons Elementor plugin allows unauthorized access to sensitive functionality due to missing capability checks and proper permission validation. This enables unauthenticated or low-privilege users to potentially modify plugin settings or access data they should not have access to.

MitigationUpdate Exclusive Addons Elementor to the latest version containing the security patch, or add WordPress capability checks and nonce verification to all AJAX actions and sensitive functions within the plugin.

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
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 Exclusive Addons for Elementor is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Exclusive Addons for Elementor' or check the plugins directory for the exclusive-addons-for-elementor folder
    Affected if The plugin is installed and active
  2. Check installed version number
    In WordPress admin > Plugins, find Exclusive Addons for Elementor and view the version number displayed beneath the plugin name, or check version in plugin main PHP file header
    Affected if Version is less than 2.6.9.2 (e.g., 2.6.9, 2.6.8, etc.)
  3. Inspect AJAX action capability checks
    Examine the plugin PHP files, specifically any AJAX handlers (usually in includes/ or classes/ folders). Look for wp_doing_ajax() conditions and current_user_can() calls before sensitive operations
    Affected if AJAX actions lack current_user_can() capability verification or nonce validation
  4. Test unauthorized access to plugin settings
    Attempt to access plugin settings pages or submit settings changes while logged out or as a low-privilege user (subscriber role)
    Affected if Sensitive plugin settings or data are accessible or modifiable without proper authorization

User is affected if Exclusive Addons for Elementor plugin is installed with version less than 2.6.9.2 and unauthenticated or low-privilege users can access plugin settings or AJAX functionality.

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.2 or later
Fixed in 2.6.9.2
Interim mitigation

Update Exclusive Addons Elementor to the latest version containing the security patch, or add WordPress capability checks and nonce verification to all AJAX actions and sensitive functions within the plugin.

Recommended fix High confidence

2.6.9.2 or latest available version

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. 3. Locate 'Exclusive Addons for Elementor' in the plugins list
  4. 4. Verify the current installed version is below 2.6.9.2
  5. 5. Update the plugin to version 2.6.9.2 or the latest available version
  6. 6. Confirm the update was successful by checking the installed version number

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

Fix this in Exclusive Addons For Elementor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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