Skip to main content
Vulnerability Database/CVE-2026-94573

CVE-2026-94573: Elementor Forms Plugin XSS Vulnerability

CVE-2026-94573 is a stored cross-site scripting vulnerability in the Repeater Fields for Elementor Forms WordPress plugin that lets unauthenticated attackers inject malicious scripts. This post covers technical details, affected versions, impact analysis, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-94573 Overview

CVE-2026-94573 is a Stored Cross-Site Scripting (XSS) vulnerability [CWE-79] in the Repeater Fields for Elementor Forms plugin for WordPress. All versions up to and including 2.2.7 are affected. The root cause is insufficient input sanitization and output escaping of the Repeater Field Value. Unauthenticated attackers can inject arbitrary web scripts that execute when any user accesses an affected page. The injected payload persists in the WordPress database, enabling session theft, credential harvesting, administrative action forgery, and malicious redirects.

Critical Impact

Unauthenticated attackers can store JavaScript payloads that execute in every visitor's browser, including administrators, leading to account takeover and site compromise.

Affected Products

  • Repeater Fields for Elementor Forms plugin for WordPress — versions ≤ 2.2.7
  • WordPress sites with the repeater-for-elementor plugin installed and active
  • Elementor Forms deployments using repeater field functionality

Discovery Timeline

  • 2026-09-25 - CVE-2026-94573 published to NVD
  • 2026-09-25 - Last updated in NVD database

Technical Details for CVE-2026-94573

Vulnerability Analysis

The vulnerability resides in the Repeater Fields for Elementor Forms plugin, which allows users to create dynamic repeating form fields. User-supplied values submitted through the repeater field are stored and later rendered without proper sanitization or output escaping. The flawed handling is documented in the plugin source at fields/repeater_end.php (lines 237, 309, and 317) and in libs/admin.js (line 15), referenced in the WordPress Plugin Trac. Because the plugin accepts input from unauthenticated form submitters, any visitor can store a JavaScript payload. The payload executes in the browser of any user who later views the affected page, including authenticated administrators.

Root Cause

The plugin fails to apply WordPress sanitization functions such as sanitize_text_field() on input and esc_html() or esc_attr() on output when handling repeater field values. The relevant code paths in repeater_end.php concatenate attacker-controlled data directly into HTML attributes or body content. This classifies the flaw as [CWE-79]: Improper Neutralization of Input During Web Page Generation.

Attack Vector

The attack vector is network-based and requires no authentication or user interaction beyond visiting an affected page. An attacker submits a crafted form containing script tags or event handler payloads within a repeater field. The payload is persisted to the WordPress database by the plugin. When any subsequent visitor renders the page containing the stored value, the browser parses the injected markup and executes attacker-controlled JavaScript in the context of the vulnerable site's origin. See the Wordfence Vulnerability Report and the WordPress Change Set Log for technical details.

Detection Methods for CVE-2026-94573

Indicators of Compromise

  • Repeater field entries in wp_postmeta or plugin tables containing <script>, onerror=, onload=, or javascript: strings.
  • Unexpected outbound requests from admin browsers to attacker-controlled domains after loading pages with Elementor forms.
  • New administrator accounts, modified user roles, or unexplained plugin installations following form submissions.
  • Web server access logs showing POST requests to Elementor form endpoints with URL-encoded HTML or JavaScript payloads.

Detection Strategies

  • Audit stored form submissions for HTML or JavaScript syntax in repeater field values using database queries filtering on <, >, and common XSS keywords.
  • Deploy a Web Application Firewall (WAF) rule set that inspects POST bodies to Elementor form endpoints for script content.
  • Enable Content Security Policy (CSP) reporting to detect inline script execution attempts on pages rendering repeater field output.

Monitoring Recommendations

  • Monitor WordPress wp-admin sessions for anomalous activity originating from administrator accounts shortly after page visits.
  • Alert on plugin or theme file modifications and new privileged user creation events.
  • Correlate form submission timestamps with subsequent administrator browser telemetry to identify payload execution.

How to Mitigate CVE-2026-94573

Immediate Actions Required

  • Update the Repeater Fields for Elementor Forms plugin to a version later than 2.2.7 once the vendor publishes a fixed release.
  • If no patched version is available, deactivate and remove the repeater-for-elementor plugin from affected WordPress sites.
  • Review all existing repeater field data in the database and remove entries containing HTML or JavaScript content.
  • Rotate credentials for any administrator who accessed pages containing untrusted form submissions.

Patch Information

The vendor commit referenced in the WordPress Change Set Log addresses the sanitization and escaping gaps in repeater_end.php and admin.js. Site administrators should upgrade to the latest plugin release through the WordPress plugin dashboard and verify the installed version is greater than 2.2.7.

Workarounds

  • Restrict access to Elementor form submission endpoints using a WAF rule blocking payloads containing <script, onerror=, or javascript:.
  • Apply a strict Content Security Policy that disallows inline scripts (script-src 'self') on pages rendering repeater field output.
  • Disable the repeater field feature in Elementor forms until the plugin is updated.
  • Limit form submissions to authenticated users via a reverse proxy or WordPress membership plugin where business requirements permit.
bash
# Example CSP header to mitigate stored XSS execution
Header set Content-Security-Policy "default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'self'"

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.