dbcve.org
Unlimited Elements For ElementorWordPress extension · Unlimited Elements

CVE-2023-31231

MEDIUM · 6.5 CVSS v3.1 Published 2023-12-20
Fix available
A fix is available. Upgrade to 1.5.66 or later.
See remediation →
71/100
Remediation priority · Elevated
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).This issue affects Unlimited Elements For Elementor (Free Widgets, Addons, Templates): from n/a through 1.5.65.

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

Unrestricted file upload vulnerability in the Unlimited Elements For Elementor WordPress plugin (versions through 1.5.65) allows attackers to upload dangerous file types (likely executable scripts like PHP files) to the affected system, potentially leading to remote code execution.

MitigationUpdate Unlimited Elements For Elementor to the latest version (greater than 1.5.65). If immediate update is not possible, consider disabling the plugin or implementing server-side file upload restrictions (e.g., web server configuration to block executable uploads in upload directories).

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

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

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. Check if Unlimited Elements For Elementor plugin is installed
    Inspect the WordPress plugins directory at wp-content/plugins/ for a folder named 'unlimited-elements-for-elementor' or check via WP admin panel under Plugins > Installed Plugins
    Affected if The plugin folder exists in the WordPress installation
  2. Identify the installed plugin version
    Open the main plugin file (typically unlimited-elements-for-elementor.php) and locate the version comment in the file header, or check the readme.txt file for the 'Stable tag' version entry
    Affected if The version listed is below 1.5.66 (e.g., 1.5.65, 1.5.64, etc.)
  3. Verify the upload functionality is accessible
    Check if the plugin's upload functionality is enabled by examining the plugin settings in the WordPress admin dashboard under the plugin's settings panel, or look for upload-related PHP files in the plugin directory
    Affected if The upload feature is enabled and accessible to users (particularly unauthenticated or low-privilege users)
  4. Inspect upload directories for suspicious files
    Examine the wp-content/uploads/ directory and any custom upload paths configured for the plugin, looking for unexpected file extensions such as .php, .phtml, .php5, or other executable file types that should not be present
    Affected if Executable files (especially PHP scripts) are found in upload directories, indicating potential exploitation

You are affected if the Unlimited Elements For Elementor plugin is installed with a version lower than 1.5.66 and the upload feature is accessible to attackers.

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.66 or later
Fixed in 1.5.66
Interim mitigation

Update Unlimited Elements For Elementor to the latest version (greater than 1.5.65). If immediate update is not possible, consider disabling the plugin or implementing server-side file upload restrictions (e.g., web server configuration to block executable uploads in upload directories).

Recommended fix High confidence

1.5.66

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate "Unlimited Elements For Elementor" in the plugin list
  4. 4. If an update is available, click "Update Now" to upgrade to version 1.5.66 or later
  5. 5. Alternatively, navigate to Dashboard > Updates and apply all available updates
  6. 6. After updating, verify the plugin version is 1.5.66 or higher 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
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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