CVE-2026-18146 json
Fluent Forms <= 6.2.11 - Unauthenticated Stored Cross-Site Scripting via Notification Smartcode Values
published 2mo ago modified 2mo ago also EUVD-2026-57736
- 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 42%
- public exploits
- 0
- none known
Summary
The Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Notification Smartcode Values in all versions up to, and including, 6.2.11 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts that execute in the browser of an administrator (or any user with the Fluent Forms entry-viewing capability) when they view the form's entry Submission Logs in the WordPress admin dashboard. Exploitation requires that a site administrator or Fluent Forms manager has configured an email notification whose subject or static (direct) Send To value references an attacker-influenced Smartcode such as an input_password field value, a cookie value, or submission.response.
Is CVE-2026-18146 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
- 2mo ago
Exploit prediction
0.49% chance of exploitation in the next 30 days, higher than 42% 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
- wpmanageninja Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/643f92e2-b14e-4056-97fc-1c631027c54f?source=cve
- plugins.trac.wordpress.org /browser/fluentform/tags/6.2.8/app/Services/FormBuilder/Notifications/EmailNotification.php#L196
- plugins.trac.wordpress.org /browser/fluentform/tags/6.2.8/boot/globals.php#L98
- plugins.trac.wordpress.org /browser/fluentform/tags/6.2.8/app/Services/FormBuilder/ShortCodeParser.php#L145
- plugins.trac.wordpress.org /browser/fluentform/tags/6.2.8/app/Services/FormBuilder/ShortCodeParser.php#L142
- plugins.trac.wordpress.org /browser/fluentform/tags/6.2.8/assets/js/form_entries.js#L2
- plugins.trac.wordpress.org /changeset?reponame=&new=3640683%40fluentform%2Ftags%2F6.2.12&old=3632883%40fluentform%2Ftags%2F6.2.11
- plugins.trac.wordpress.org /changeset/3640683/fluentform/trunk/app/Services/FormBuilder/ShortCodeParser.php
- plugins.trac.wordpress.org /changeset?old_path=%2Ffluentform/tags/6.2.11&new_path=%2Ffluentform/tags/6.2.12
Sources
- CVE List CVE-2026-18146
- NVD CVE-2026-18146
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.