dbcve.org
Unlimited Elements For ElementorWordPress extension · Unlimited Elements

CVE-2023-31090

HIGH · 8.8 CVSS v3.1 Published 2024-04-24
Fix available
A fix is available. Upgrade to 1.5.61 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
Unrestricted Upload of File with Dangerous Type vulnerability in Unlimited Elements Unlimited Elements For Elementor (Free Widgets, Addons, Templates) allows Upload a Web Shell to a Web Server.This issue affects Unlimited Elements For Elementor (Free Widgets, Addons, Templates): from n/a through 1.5.60.

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 plugin before version 1.5.61 contains an unrestricted file upload vulnerability that allows attackers to upload executable files (web shells) to the web server. This vulnerability enables remote code execution by allowing dangerous file types (such as PHP scripts) to be uploaded without proper validation and access controls.

MitigationUpdate Unlimited Elements For Elementor to version 1.5.61 or later to patch the unrestricted file upload vulnerability. Until patched, monitor for suspicious PHP file uploads and disable the plugin if immediate patching is not possible.

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

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 the plugin is installed
    Check if the Unlimited Elements For Elementor plugin exists in the WordPress plugins directory (wp-content/plugins/). Access this via FTP, file manager, or the WordPress admin plugins page.
    Affected if The plugin is present on the WordPress site.
  2. Check the installed version
    In WordPress admin, go to Plugins > Installed Plugins and find Unlimited Elements For Elementor. Note the version number displayed. Alternatively, check the main plugin file header in wp-content/plugins/unlimited-elements-for-elementor/ for the Version field.
    Affected if The installed version is lower than 1.5.61.
  3. Confirm the plugin is active
    In WordPress admin > Plugins, verify whether Unlimited Elements For Elementor is activated. An inactive plugin still poses risk if the files remain on the server.
    Affected if The plugin is activated.
  4. Review recent uploads for suspicious files
    Inspect the wp-content/uploads/ directory (and year/month subdirectories) for any unexpected .php, .phtml, .php5, or other executable files that were uploaded recently. Check file creation timestamps.
    Affected if Unexpected PHP files or other executable scripts are found in the uploads directory.

A WordPress site with Unlimited Elements For Elementor installed and active at a version lower than 1.5.61 is affected by this unrestricted file upload vulnerability.

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.61 or later
Fixed in 1.5.61
Interim mitigation

Update Unlimited Elements For Elementor to version 1.5.61 or later to patch the unrestricted file upload vulnerability. Until patched, monitor for suspicious PHP file uploads and disable the plugin if immediate patching is not possible.

Recommended fix High confidence

Unlimited Elements For Elementor version 1.5.61

  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. Click 'Update now' if an update is available, or manually update to version 1.5.61 or higher
  5. Verify the plugin version after update by checking the plugins page

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

Fix this in Unlimited Elements For Elementor Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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