WordPress security changelog
MEDIUM CVE-2026-75586 Deferred

Unlimited Elements reflects script through its public form handler

Unlimited Elements for Elementor through 2.0.17 exposes a front-end handler on the public wp action without a nonce, capability, or referer check. Attacker-controlled formData[id] is inserted into an exception message and returned without escaping; when served as HTML, a victim who follows the crafted request executes the reflected script.

CVE / CNA score 6.1 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Unlimited Elements For Elementor
Plugin slug
unlimited-elements-for-elementor
Affected
<= 2.0.17
Safe version
See mitigation notes
Published
Sep 05, 2026
Weakness
CWE-79 — Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

This CVE was published Sep 05, 2026 and is one of 42 known issues for this plugin.

Update, patch or deactivate.

Version 2.0.18 is available and may resolve the issue, but its official changelog does not confirm this CVE. Update conservatively, restrict the affected public handler until remediation is confirmed, and invalidate privileged sessions if a crafted link was opened.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Technical description

The Unlimited Elements For Elementor plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via 'formData[id]' Parameter in all versions up to, and including, 2.0.17 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. The front-end AJAX handler is registered on the public 'wp' action with no nonce, capability, or referer check, and the raw attacker-controlled id value is interpolated verbatim into an exception message that is echoed back without escaping; when the response is served as text/html rather than application/json, the browser parses the injected markup.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Primary and upstream sources