CVE-2026-94573 json
Repeater Fields for Elementor Forms <= 2.2.7 - Unauthenticated Stored Cross-Site Scripting via Repeater Field Value
published 2026-09-25 45 d ago modified 2026-09-25 44 d ago also EUVD-2026-86578
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
The Repeater Fields for Elementor Forms plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Repeater Field Value in all versions up to, and including, 2.2.7 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 45 d ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N |
Affected products
- addonsorg Repeater Fields for Elementor Forms
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/ea28fc6c-50d6-406b-9205-3f1bec577644?source=cve
- plugins.trac.wordpress.org /browser/repeater-for-elementor/tags/2.2.7/libs/admin.js#L15
- plugins.trac.wordpress.org /browser/repeater-for-elementor/tags/2.2.7/fields/repeater_end.php#L317
- plugins.trac.wordpress.org /browser/repeater-for-elementor/tags/2.2.7/fields/repeater_end.php#L309
- plugins.trac.wordpress.org /browser/repeater-for-elementor/tags/2.2.7/fields/repeater_end.php#L237
- plugins.trac.wordpress.org /changeset?reponame=&old=3710785%40repeater-for-elementor&new=3710785%40repeater-for-elementor
Sources
- CVE List CVE-2026-94573
- NVD CVE-2026-94573
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.