CVE-2026-18325 json
Forminator Forms <= 1.56.1 - Unauthenticated Stored Cross-Site Scripting via Forged Upload Record via Select Field
published 3mo ago modified 2mo ago also EUVD-2026-53704
- 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 41%
- public exploits
- 0
- none known
Summary
The Forminator Forms – Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Forged Upload Record via Select Field in all versions up to, and including, 1.56.1 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. The exploit is possible because Forminator_Core::sanitize_array() skips all filtering for keys prefixed with 'select-', and set_field_data() treats a submitted 'return' member as a trusted internal flag — allowing an unauthenticated attacker to forge and persist a complete upload field record with an arbitrary file_url value without any sanitization or validation.
Is CVE-2026-18325 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
- yes
- Technical impact
- partial
- Assessed
- 3mo ago
Exploit prediction
0.48% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-09).
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
- wpmudev Forminator Forms – Contact Form, Payment Form & Custom Form Builder
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/fd9a81eb-2211-42e9-a456-fb60f3ca2c0f?source=cve
- plugins.trac.wordpress.org /browser/forminator/tags/1.56.0/library/model/class-form-entry-model.php#L1569
- plugins.trac.wordpress.org /browser/forminator/tags/1.56.0/library/modules/custom-forms/front/front-action.php#L1091
- plugins.trac.wordpress.org /browser/forminator/tags/1.56.0/library/class-core.php#L616
- plugins.trac.wordpress.org /browser/forminator/tags/1.56.0/library/abstracts/abstract-class-front-action.php#L127
- plugins.trac.wordpress.org /browser/forminator/tags/1.55.1/library/model/class-form-entry-model.php#L1569
- plugins.trac.wordpress.org /browser/forminator/tags/1.55.1/library/modules/custom-forms/front/front-action.php#L1091
- plugins.trac.wordpress.org /browser/forminator/tags/1.55.1/library/class-core.php#L616
- plugins.trac.wordpress.org /browser/forminator/tags/1.55.1/library/abstracts/abstract-class-front-action.php#L127
- plugins.trac.wordpress.org /changeset?reponame=&new=3628716%40forminator%2Ftrunk&old=3628530%40forminator%2Ftrunk
Sources
- CVE List CVE-2026-18325
- NVD CVE-2026-18325
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.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.