CVE-2026-18146: Fluent Forms (WordPress plugin) · Cross-site Scripting
Affects Fluent Forms (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 9 Nov 2026, 23:24 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| wpmanageninjaFluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder | Affected
| Fixed in– |
AI-suggested
Until an official fix is available, administrators should avoid viewing submission logs that may contain attacker-controlled Smartcodes or disable email notifications referencing untrusted Smartcode values. Monitoring vendor channels for updates and applying patches promptly once released is recommended.
Description
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.
References
- wordfence.com/threat-intel/vulnerabilities/id/643f92e2-b14e-4056-97fc-1c631027c54f?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/fluentform/tags/6.2.8/app/Services/FormBuilder/Notifications/EmailNotification.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/fluentform/tags/6.2.8/boot/globals.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/fluentform/tags/6.2.8/app/Services/FormBuilder/ShortCodeParser.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/fluentform/tags/6.2.8/app/Services/FormBuilder/ShortCodeParser.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/fluentform/tags/6.2.8/assets/js/form_entries.js (opens in a new tab)
- plugins.trac.wordpress.org/changeset?reponame=&new=3640683%40fluentform%2Ftags%2F6.2.12&old=3632883%40fluentform%2Ftags%2F6.2.11 (opens in a new tab)
- plugins.trac.wordpress.org/changeset/3640683/fluentform/trunk/app/Services/FormBuilder/ShortCodeParser.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset?old_path=%2Ffluentform/tags/6.2.11&new_path=%2Ffluentform/tags/6.2.12 (opens in a new tab)