dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-27041

CRITICAL · 9.9 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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
Contributor Arbitrary File Upload in Unlimited Elements for Elementor (Premium) <= 2.0.6 versions.

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

Arbitrary file upload vulnerability in Unlimited Elements for Elementor (Premium) plugin versions 2.0.6 and below allows users with Contributor-level permissions to upload arbitrary files to the server, potentially leading to remote code execution.

MitigationUpdate Unlimited Elements for Elementor to a version newer than 2.0.6. Until patched, disable file upload capabilities for Contributor role users or temporarily disable the plugin.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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
    Navigate to WordPress admin > Plugins and locate 'Unlimited Elements for Elementor' in the installed plugins list
    Affected if Plugin is not installed means not affected
  2. Check installed version
    In Plugins list, click on the plugin to view details, or check the plugin header in wp-content/plugins/unlimited-elements-for-elementor/includes/uc-plugin.php for version number
    Affected if Version 2.0.6 or lower means potentially affected
  3. Identify user role capabilities
    Navigate to WordPress admin > Users > Roles > Contributor (or use a role editor plugin) to view capabilities assigned to Contributor role
    Affected if Contributor role has upload_files or similar file upload capabilities enabled means potentially affected
  4. Check for upload functionality
    Inspect the plugin files in wp-content/plugins/unlimited-elements-for-elementor for upload-related PHP files (e.g., upload.php, ajax_upload.php, or similar)
    Affected if Upload functionality files exist and are accessible means potentially affected

User is affected if Unlimited Elements for Elementor plugin version 2.0.6 or lower is installed AND Contributor role has file upload capabilities enabled.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Unlimited Elements for Elementor to a version newer than 2.0.6. Until patched, disable file upload capabilities for Contributor role users or temporarily disable the plugin.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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