Fluent Forms <= 6.2.1 - Incorrect Authorization to Authenticated (Subscriber+) Arbitrary Subscription Cancellation via 'subscription_id'
Strategic Overview
- Status
- Patched in 6.2.2
- Affected Plugin
- Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder
- Affected Version
<= 6.2.1- CVSS
- 5.4Medium
- Weakness type
- CWE-863 · Incorrect Authorization
- CVE
CVE-2026-5069
At a glance
CVE-2026-5069 is a medium-severity Incorrect Authorization vulnerability in the Fluent Forms WordPress plugin, affecting versions <= 6.2.1. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 6.2.2; sites on affected versions should update now. Disclosed July 2026, reported by Fernando Mecozzi.
Vulnerability Overview
The Fluent Forms plugin for WordPress is vulnerable to incorrect authorization via the 'subscription_id' parameter in versions up to, and including, 6.2.1. This is due to insufficient ownership authorization checks in the payment cancellation AJAX flow. This makes it possible for authenticated attackers, with subscriber-level access and above, to submit cancellation requests for other users' subscriptions.
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-863: Incorrect Authorization
Fluent Forms <= 6.2.1 carries this weakness at subscription_id, and reaching it takes an account at Subscriber level or above. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.
The action runs for users the code intended to exclude, with the same effect as having no check at all. For Fluent Forms the fix is 6.2.2: builds <= 6.2.1 are affected, anything from 6.2.2 onward is not.
Remediation
Update to version 6.2.2, 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.2 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder
- 9.8CVE-2024-2771: Contact Form Plugin… Settings Update and Limited
CVE-2024-2771 - 8.8CVE-2021-34620: WP Fluent Forms < 3.6.67 Stored Cross-Site Scripting
CVE-2021-34620 - 8.3CVE-2022-3463: Contact Form Plugin by FluentForm CSV Injection
CVE-2022-3463 - 8.2CVE-2026-5395: Fluent Forms <= 6.2.0 Authorization Bypass
CVE-2026-5395 - 8.2CVE-2026-5396: Fluent Forms <= 6.1.21 Authorization Bypass
CVE-2026-5396 - 7.5CVE-2024-4157: Contact Form Plugin… PHP Object Injection
CVE-2024-4157 - 7.5CVE-2024-2782: Contact Form Plugin… Setting Manipulation
CVE-2024-2782 - 7.2CVE-2026-18146: Fluent Forms <= 6.2.11 Stored Cross-Site Scripting
CVE-2026-18146
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C