dbcve.org
Unlimited Elements For ElementorWordPress extension · Unlimited Elements

CVE-2023-33930

HIGH · 7.2 CVSS v3.1 Published 2024-06-04
Fix available
A fix is available. Upgrade to 1.5.67 or later.
See remediation →
78/100
Remediation priority · High
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 Code Injection.This issue affects Unlimited Elements For Elementor (Free Widgets, Addons, Templates): from n/a through 1.5.66.

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

Unrestricted file upload vulnerability in the Unlimited Elements For Elementor plugin allows authenticated attackers to upload files with dangerous types (likely executable PHP files) leading to code injection/remote code execution. The plugin fails to properly validate uploaded file types before storing them in accessible web directories.

MitigationUpdate the plugin to version 1.5.67 or later which contains the security fix. Until patched, disable the plugin or restrict upload functionality via web application firewall rules.

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

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

CVSS:3.1/AV:N/AC:L/PR:H/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 installation
    Locate the plugin directory: /wp-content/plugins/unlimited-elements-for-elementor/ or check via WordPress admin under Plugins > Installed Plugins
    Affected if Plugin is present in the WordPress installation
  2. Check installed version
    Open the main plugin file (e.g., unlimited-elements-for-elementor.php) and locate the version in the plugin header comment, or check the version in WordPress admin plugin list
    Affected if Version displayed is below 1.5.67 (e.g., 1.5.66, 1.5.65, etc.)
  3. Confirm upload functionality is accessible
    Check if the plugin uploads directory /wp-content/uploads/unlimited-elements/ exists and is web-accessible; the vulnerability affects the file upload endpoint within the plugin
    Affected if Uploads directory exists and is reachable via HTTP (default plugin behavior)

If the installed version of Unlimited Elements For Elementor is below 1.5.67 and the plugin upload functionality is accessible, the environment 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.67 or later
Fixed in 1.5.67
Interim mitigation

Update the plugin to version 1.5.67 or later which contains the security fix. Until patched, disable the plugin or restrict upload functionality via web application firewall rules.

Recommended fix High confidence

1.5.67

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Unlimited Elements For Elementor' plugin
  4. Check the current version number to confirm it is below 1.5.67
  5. Click 'Update Now' on the plugin to update to the latest version, which includes the fix (version 1.5.67 or later)
  6. Verify the update completed successfully and the plugin is now at version 1.5.67 or higher
  7. Consider reviewing uploaded files directory for any suspicious files that may have been uploaded during the vulnerability window

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 / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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