CVE-2023-3295
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 · uneditedThe Unlimited Elements For Elementor (Free Widgets, Addons, Templates) for WordPress is vulnerable to arbitrary file uploads due to missing file type validation of files in the file manager functionality in versions up to, and including, 1.5.66 . This makes it possible for authenticated attackers, with contributor-level permissions and above, to upload arbitrary files on the affected site's server which may make remote code execution possible. The issue was partially patched in version 1.5.66 and fully patched in 1.5.67. CVE-2023-31231 appears to be a duplicate of this issue.
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 confidenceThe Unlimited Elements For Elementor WordPress plugin lacks file type validation in its file manager functionality, allowing authenticated users with contributor-level permissions or higher to upload arbitrary files to the server. This arbitrary file upload vulnerability can lead to remote code execution.
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< 1.5.67CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify plugin installation and activation statusCheck if the Unlimited Elements For Elementor plugin is installed and active in the WordPress environment by inspecting the plugins admin page or checking for the plugin directory at wp-content/plugins/unlimited-elements-for-elementor/Affected if Plugin is installed and active, exposing the file manager functionality
-
Identify installed plugin versionLocate the main plugin file (typically unlimited-elements-for-elementor.php) and read the version header declared in the plugin comments, or query the wp_options table for the option_name containing the plugin versionAffected if Version is lower than 1.5.67 (e.g., 1.5.66, 1.5.65, etc.)
-
Confirm file manager feature is accessibleDetermine whether the plugin file manager functionality is enabled or accessible by checking the plugin settings in the WordPress admin panel under the Unlimited Elements settings, or by inspecting any file-manager-related options in the wp_options tableAffected if File manager feature is enabled or not explicitly disabled in plugin configuration
-
Enumerate user accounts with contributor-level or higher accessQuery the wp_usermeta table to identify users with wp_capabilities meta_value containing contributor, author, editor, or administrator roles; or review the Users admin page for accounts with these permission levelsAffected if At least one user account with contributor-level permissions or higher exists in the WordPress installation
The environment is affected if the Unlimited Elements For Elementor plugin is installed with a version below 1.5.67, the file manager feature is accessible, and at least one user with contributor-level permissions or higher exists.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.5.67
Update the plugin to version 1.5.67 or later to apply the full patch. Until updated, restrict contributor-level access or temporarily disable the plugin to prevent exploitation.
1.5.67
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Find "Unlimited Elements For Elementor" in the plugin list
- If an update is available, click "Update Now" to update to version 1.5.67 or later
- Alternatively, download version 1.5.67 or later from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin
- After updating, verify the version number shows 1.5.67 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2023-3295 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-3295 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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