Safeguard
Vulnerability Analysis•

CVE-2023-33930: Critical File Upload Flaw in Unlimited Elements

CVE-2023-33930 is a critical zip extraction flaw in Unlimited Elements for Elementor through 1.5.66. Update the plugin and check for stray files.

Safeguard Security Team
3 min read

CVE-2023-33930 is a critical (CVSS 9.1) unrestricted file upload flaw in the Unlimited Elements for Elementor WordPress plugin, versions through 1.5.66. It allows code injection through unrestricted zip extraction. Update to the latest plugin release and check the site for files you did not add.

What's affected

  • Unlimited Elements for Elementor (Free Widgets, Addons, Templates), all versions from n/a through 1.5.66, per the NVD record.
  • The record does not state a fixed version, and the Patchstack page that it references could not be retrieved for this review. Check the plugin changelog for the release that closed the issue.

The weakness class is CWE-434, unrestricted upload of a file with a dangerous type. The Patchstack page title describes it as unrestricted zip extraction.

How to check if you're exposed

If you manage the site with WP-CLI, list the plugin and its version:

wp plugin list --name=unlimited-elements-for-elementor --fields=name,version,status,update

Without WP-CLI, open the Plugins page in the WordPress dashboard and read the version under the plugin name. Any version up to and including 1.5.66 is in the affected range.

Then look for signs of misuse. Check the uploads folder and the plugin folders for PHP files or archives you did not add, and compare file modification dates with your last known change. Look in access logs for unexpected requests to the plugin endpoints.

What to do now

  1. Update Unlimited Elements for Elementor to the newest release from the WordPress plugin directory. Take a backup first.
  2. If you cannot update right away, deactivate and remove the plugin until you can.
  3. Scan the site files for PHP files in upload directories and for recently changed files, and remove anything you cannot explain.
  4. Reset administrator passwords and check for unknown administrator accounts if you found suspicious files.
  5. Limit which users can install or extract archives, and set the web server to refuse PHP execution inside the uploads folder.

If you track software dependencies, the free in-browser dependency scan can show which of your components carry known CVEs, and the Gold directory lists the same records in one place.

Why it matters

Features that unpack zip files on a server are risky because the archive can contain files the site never meant to accept. If the plugin does not check what it extracts and where it puts it, an upload feature turns into a way to place code on the server. The record calls the result code injection.

WordPress plugins are a common source of this class of bug because each plugin adds its own upload handling. The defensive pattern is to allow only expected file types, extract to a safe directory, and never allow execution of uploaded content.

The record shows this CVE is not in the CISA Known Exploited Vulnerabilities catalog, and we found no advisory that reports exploitation in the wild.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

Which version fixes it?

The record only says versions through 1.5.66 are affected. Check the plugin changelog or the Patchstack entry for the first fixed release.

Do I need an account on the site to be hit?

The record does not state this. Treat the issue as reachable until the vendor information says otherwise.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.