Unlimited Elements For Elementor Plugin Vulnerability (CVE-2026-87092)

On this page

Security Alert Summary

The Unlimited Elements For Elementor plugin contains a directory traversal vulnerability that allows authenticated users with contributor-level access or higher to read arbitrary files on the server. The issue is reachable via the get_addon_output_data AJAX endpoint because the nonce protecting that endpoint is exposed on the Elementor editor page, which Contributors can access. The problematic file-reading logic is implemented in the getFileContentByUrl function.

CVE Details

  • CVE ID: CVE-2026-87092
  • Affected component: Unlimited Elements for Elementor plugin for WordPress
  • Affected versions: all versions up to and including 2.0.26
  • Published: November 21, 2026 at 10:16:52 AM
  • Last modified: November 21, 2026 at 10:16:53 AM
  • CVSS v3.1: Base score 6.5, MEDIUM — Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
  • Authentication / privileges / user interaction: Requires an authenticated user. Privileges required: Low (contributor-level access or above). User interaction: None.
  • Primary impact: Confidentiality: High; Integrity: None; Availability: None
  • Weakness: CWE-22 (Directory Traversal)

Technical Details

The plugin exposes an AJAX endpoint named get_addon_output_data and emits a nonce for that endpoint on the Elementor editor page. Because Contributors can access the Elementor editor, the nonce and endpoint are reachable by authenticated users at that privilege level or above. The vulnerable code path is in the getFileContentByUrl function, which performs file retrieval without adequate directory traversal protections. An attacker who can call this function via the reachable AJAX endpoint can request files outside the intended directory, resulting in disclosure of file contents.

The impact is limited to file disclosure: an attacker can read arbitrary files the web server process can access. The vulnerability does not, based on the provided information, indicate direct modification of files or denial of service.

How This Could Impact Your Website

In a typical small or medium business WordPress site, multiple users may have different roles: a site owner, editors, internal staff contributors, and external contractors or content contributors. If a contributor-level account is able to access the Elementor editor, that user could leverage this vulnerability to read files on the server. Stolen files might include configuration files, backups, or other sensitive data that contain credentials or internal email lists.

Practical consequences include exposure of internal user email addresses and increased risk of targeted phishing or social engineering against staff and contractors. If sensitive configuration files are disclosed, attackers may gain additional information useful for further attacks, though the available data indicates read-only access to files rather than direct code modification.

If you\’re unsure whether your site is affected or how to assess your current user roles and plugins, it may be worth having a professional review your setup.

Recommended Actions

  • Update the affected plugin as soon as a patched version is available.
  • Review and reduce unnecessary user roles, especially contributor accounts.
  • Enforce strong, unique passwords and enable two-factor authentication for editors and administrators.
  • Remove unused or unmaintained plugins from your site.
  • Monitor site activity and server logs for unusual file access or AJAX requests to plugin endpoints.

If you\’d like help reviewing your plugins, user roles, or overall WordPress security posture, our team at Freshy is happy to help.


References