dbcve.org
Unlimited Elements For ElementorWordPress extension · Unlimited Elements

CVE-2024-3055

HIGH · 8.8 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 1.5.105 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
The Unlimited Elements For Elementor (Free Widgets, Addons, Templates) plugin for WordPress is vulnerable to time-based SQL Injection via the ‘id’ parameter in all versions up to, and including, 1.5.102 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with contributor access or higher, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 Unlimited Elements For Elementor WordPress plugin fails to properly sanitize and escape the 'id' parameter, and lacks prepared statements in its SQL queries. This allows authenticated users with contributor-level access or higher to inject time-based SQL queries through the vulnerable parameter, potentially exfiltrating sensitive data from the database.

MitigationUpdate the plugin to version 1.5.103 or later which contains the patched code. Alternatively, restrict or disable the plugin until the update can be applied.

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

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. Verify plugin is installed
    Check the WordPress plugins directory or access Plugins > Installed Plugins in the WordPress admin dashboard and look for 'Unlimited Elements For Elementor'
    Affected if The plugin is listed in the WordPress installation
  2. Check the installed version
    In WordPress admin, go to Plugins > Installed Plugins and find the version number listed for Unlimited Elements For Elementor, or inspect the plugin header in the main plugin file
    Affected if The version number is lower than 1.5.105
  3. Confirm plugin is active
    In Plugins > Installed Plugins, verify the plugin shows as 'Active' rather than 'Inactive' or 'Network Active'
    Affected if The plugin is currently activated on the site
  4. Identify high-privilege users
    Check WordPress user roles under Users > All Users and count accounts with Contributor, Author, Editor, or Administrator roles
    Affected if There are one or more users with contributor-level access or higher (these accounts could exploit the vulnerability if compromised)

A site is affected if the Unlimited Elements For Elementor plugin is installed, active, and running version 1.5.104 or lower, and has at least one user with contributor-level access or higher.

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.105 or later
Fixed in 1.5.105
Interim mitigation

Update the plugin to version 1.5.103 or later which contains the patched code. Alternatively, restrict or disable the plugin until the update can be applied.

Recommended fix High confidence

Unlimited Elements For Elementor version 1.5.105 or later

  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. If an update is available, click 'Update Now' to upgrade to version 1.5.105 or later
  5. Alternatively, navigate to Dashboard > Updates and apply all available updates
  6. Verify the plugin version has been updated to 1.5.105 or higher after the update completes

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
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.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-3055 — 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-3055 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