CVE-2026-84293 json
Repeater Fields for Gravity Forms <= 3.0.4 - Unauthenticated Stored Cross-Site Scripting via Repeated Multi-Input Sub-Field Values
published 2mo ago modified 2mo ago also EUVD-2026-74602
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 43%
- public exploits
- 0
- none known
Summary
The Repeater Fields for Gravity Forms plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Repeated Multi-Input Sub-Field Values in all versions up to, and including, 3.0.4 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. This vulnerability only affects multi-input sub-field types within a repeater (such as Name, Address, and Checkbox fields), as scalar single-input field values are escaped with esc_html() at the output stage in version 3.0.4.
Is CVE-2026-84293 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2mo ago
Exploit prediction
0.51% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-11).
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 Gravity Forms
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/55f9bfd7-e77c-4072-a1de-36f3ac1ffb81?source=cve
- plugins.trac.wordpress.org /browser/repeater-for-gravity-forms/tags/3.0.4/fields/repeater_field.php#L549
- plugins.trac.wordpress.org /browser/repeater-for-gravity-forms/tags/3.0.4/fields/repeater_field.php#L543
- plugins.trac.wordpress.org /browser/repeater-for-gravity-forms/tags/3.0.4/fields/repeater_field.php#L401
- plugins.trac.wordpress.org /browser/repeater-for-gravity-forms/tags/3.0.4/fields/repeater_field.php#L474
- plugins.trac.wordpress.org /browser/repeater-for-gravity-forms/tags/2.4.6/fields/repeater_field.php#L549
- plugins.trac.wordpress.org /browser/repeater-for-gravity-forms/tags/2.4.6/fields/repeater_field.php#L543
- plugins.trac.wordpress.org /browser/repeater-for-gravity-forms/tags/2.4.6/fields/repeater_field.php#L401
- plugins.trac.wordpress.org /browser/repeater-for-gravity-forms/tags/2.4.6/fields/repeater_field.php#L474
- plugins.trac.wordpress.org /changeset?reponame=&old=3677164%40repeater-for-gravity-forms&new=3677164%40repeater-for-gravity-forms
Sources
- CVE List CVE-2026-84293
- NVD CVE-2026-84293
Fencer Intel 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.