dbcve.org
Unlimited Elements For ElementorWordPress extension · Unlimited Elements

CVE-2024-35674

HIGH · 8.8 CVSS v3.1 Published 2024-06-05
Fix available
A fix is available. Upgrade to 1.5.110 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Unlimited Elements Unlimited Elements For Elementor (Free Widgets, Addons, Templates) unlimited-elements-for-elementor.This issue affects Unlimited Elements For Elementor (Free Widgets, Addons, Templates): from n/a through <= 1.5.109.

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 the Unlimited Elements for Elementor WordPress plugin allows users to perform actions without proper capability verification. This could permit unauthenticated or lower-privileged users to access administrative functions they should not have permission to execute.

MitigationUpdate to the latest patched version of Unlimited Elements for Elementor once released, or implement proper capability checks and nonce verification on all sensitive AJAX actions and admin 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
Unlimited Elements For ElementorWordPress extension
Affected:< 1.5.110

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Unlimited Elements for Elementor', or check the plugin files in wp-content/plugins/unlimited-elements-for-elementor/ directory
    Affected if The plugin is installed and active on the WordPress site
  2. Identify installed version
    In WordPress admin, go to Plugins > Installed Plugins and locate the version number listed under the Unlimited Elements for Elementor plugin, or read the version in the plugin's main PHP file header (usually plugin.php or unlimited-elements.php)
    Affected if The version number is lower than 1.5.110 (for example, 1.5.100, 1.5.1, etc.)
  3. Check for exposed admin AJAX actions
    Inspect the plugin's main PHP file for add_action calls registering AJAX handlers (search for 'wp_ajax_' and 'wp_ajax_nopriv_' hooks). Use a tool like grep to search: grep -r "wp_ajax_" /path/to/wp-content/plugins/unlimited-elements-for-elementor/
    Affected if AJAX actions are registered with wp_ajax_nopriv_ (which allows unauthenticated access) and do not include capability checks using current_user_can() or nonce verification before executing sensitive operations
  4. Review capability checks in plugin functions
    Search the plugin PHP files for critical admin functions and verify they include current_user_can() capability checks. Use grep to search: grep -r "current_user_can" /path/to/wp-content/plugins/unlimited-elements-for-elementor/ and compare against AJAX handler functions
    Affected if Sensitive functions that modify settings, create content, or access admin capabilities lack proper current_user_can() verification before execution

The site is affected if Unlimited Elements for Elementor is installed with a version lower than 1.5.110 AND the plugin exposes AJAX actions accessible without authentication or lacks capability checks on administrative functions.

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

Update to the latest patched version of Unlimited Elements for Elementor once released, or implement proper capability checks and nonce verification on all sensitive AJAX actions and admin functions within the plugin.

Recommended fix Moderate confidence

1.5.110

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Unlimited Elements For Elementor' in the plugin list
  4. Check if the current version is below 1.5.110
  5. If vulnerable, click 'Update Now' to update to the latest version
  6. Alternatively, download version 1.5.110 or later from the WordPress plugin repository
  7. Deactivate the current plugin, delete it, then upload and install the new version
  8. After update, verify the plugin is running version 1.5.110 or higher

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

Fix this in Unlimited Elements For Elementor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
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,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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