CVE-2026-15178

Fluent Forms <= 6.2.5 - Missing Authorization to Authenticated (Custom+) Sensitive Data Exposure and Modification

2026-10-09 17:52
Nadir Şensoy

Strategic Overview

Status
Patched in 6.2.6
Affected Plugin
Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder
Affected Version
<= 6.2.5
CVSS
5.4Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-15178
View all Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder vulnerabilities

At a glance

CVE-2026-15178 is a medium-severity Missing Authorization vulnerability in the Fluent Forms WordPress plugin, affecting versions <= 6.2.5. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Custom level or above. The issue is fixed in version 6.2.6; sites on affected versions should update now. Disclosed October 2026, reported by Nadir Şensoy.

Vulnerability Overview

The Fluent Forms plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 6.2.5. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with Custom-level access and above, to read private form submissions, change submission statuses, permanently delete submissions, and modify global plugin settings.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in Fluent Forms <= 6.2.5 takes an account at Custom level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Fluent Forms the fix is 6.2.6: builds <= 6.2.5 are affected, anything from 6.2.6 onward is not.

Remediation

Update to version 6.2.6, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Fluent Forms 6.2.6 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-15178https://www.wordfence.com/threat-intel/vulnerabilities/id/10f5eef7-ea2f-44ee-8907-da53ced19180https://nvd.nist.gov/vuln/detail/CVE-2026-15178

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C